Software Testing Software > Software Testing Quiz > Types of software testing




←

→

Types of software testing

May 19th, 2012 | Software Testing Quiz, software testing types

Types of software testing

Below is a list of 100 Objective questions on various software testing Types, methods and techniques.  This is an easy and quick test to take.  Take the test now to find out how well you know the subject.

Congratulations - you have completed . You scored %%SCORE%% out of %%TOTAL%%. Your performance has been rated as %%RATING%%
Your answers are highlighted below.
Question 1
Black box testing is also know as Gray box testing.
A
True
B
False
Question 1 Explanation: 
Gray box testing is a combination of Black-box testing and white-box testing. Gray box testing is not exactly same as black-box testing.
Question 2
Objective of black box testing is to validate application functionality with requirements.
A
False
B
True
Question 3
Black box testing does not require to know internal structure of the progam being tested.
A
False
B
True
Question 4
Black box testing validates functional requirements but not non-functional requirements.
A
False
B
True
Question 4 Explanation: 
Black box testing also covers non-functional requirements like display, text alignment, response of the application etc.,
Question 5
Black box testing can uncover defects that cannot be found by white box testing.
A
True
B
False
Question 5 Explanation: 
Both Black box and White box testing complement each other, there are classes of errors that can be found by other. e.g. issues with text alignment in a browser window cannot be found with white box testing. There are other such error where in they can be found only by Black box testing but not with white box testing.
Question 6
 BVA (Boundary Value Analysis) is a black box testing technique.
A
False
B
True
Question 7
All-pairs testing is one of the Black box testing techniques.
A
True
B
False
Question 8
Equivalence partitioning is a black box testing technique.
A
False
B
True
Question 9
State transition table is a black box testing technique.
A
True
B
False
Question 10
Decision table is a black box testing technique.
A
False
B
True
Question 11
White box testing is also know as Glass box testing.
A
False
B
True
Question 12
White box testing is also known as Gray box testing.
A
True
B
False
Question 12 Explanation: 
Gray box testing is a combination of white box and black box testing, it's not exactly same as white box testing.
Question 13
White box testing is also known as Clear box testing.
A
False
B
True
Question 14
White box testing is also known as Structural testing.
A
True
B
False
Question 15
White box testing is also known as open box testing.
A
False
B
True
Question 16
White box testing is also known as Transparent box testing.
A
True
B
False
Question 17
Statement Coverage is a white box testing technique.
A
True
B
False
Question 18
 Decision Coverage is a white box testing technique.
A
False
B
True
Question 19
 State transition table is a white box testing technique.
A
True
B
False
Question 20
Branch testing is a white box testing technique.
A
True
B
False
Question 21
Data flow testing is a white box testing technique.
A
True
B
False
Question 22
Path testing is a white box testing technique.
A
False
B
True
Question 23
White box testing involves testing internal structure of programs.
A
False
B
True
Question 24
Programming skills are required to perform white box testing.
A
True
B
False
Question 25
White box testing is usually done by developers.
A
False
B
True
Question 26
White box testing techniques are required to perform Unit testing.
A
True
B
False
Question 27
Which type of testing can find dead code ?
A
Black box testing
B
White box testing
C
Both White box and black box testing
Question 28
White box testing can find redundant code.
A
False
B
True
Question 29
White box testing can find errors associated with loops.
A
False
B
True
Question 30
White box test cases cannot be automated.
A
False
B
True
Question 30 Explanation: 
White box test cases can be automated, there are tools like Junit for Java, using which Unit test cases for Java programs can be automated. Similary there are other unit testing tools like NUnit for C# etc.,
Question 31
Smoke testing and Sanity Testing are one and the same.
A
True
B
False
Question 31 Explanation: 
Sanity testing is to check if new functionality and test environment is stable to continue with testing. Smoke testing is to check if all the important functionaltiy is working fine so that detailed testing can be carried out.
Question 32
Sanity test cases are usually  not documented.
A
False
B
True
Question 33
Sanity testing is a very high level check of the functionality and environment.
A
True
B
False
Question 34
Sanity testing is done before running Regression tests.
A
True
B
False
Question 35
Smoke testing is performed after regression testing is completed.
A
True
B
False
Question 36
Smoke testing is carried out before performing other major tests.
A
False
B
True
Question 37
Smoke testing is done to confirm important functionality are working as expected.
A
False
B
True
Question 38
Objective of Smoke testing is to catch show stopper defects as early as possible.
A
True
B
False
Question 39
Smoke tests are a subset of regression tests.
A
False
B
True
Question 40
Smoke test cases are not documented.
A
False
B
True
Question 40 Explanation: 
Smoke test cases are usually documented.
Question 41
Smoke test cases are not a good candidate for automation.
A
True
B
False
Question 41 Explanation: 
Smoke test cases are ideal to automate, as they are run more often, almost on every new build provided for testing.
Question 42
Unit testing has to be performed by developers.
A
True
B
False
Question 43
Unit testing requires understanding of interal logic and structure.
A
False
B
True
Question 44
Unit tests cannot be automated.
A
True
B
False
Question 45
Unit testing by developers and functional testing by testers can be done in parallel.
A
True
B
False
Question 45 Explanation: 
Functional testing is started only after Unit testing is completed.
Question 46
Unit testing does not require any documentation.
A
True
B
False
Question 46 Explanation: 
Unit tests need to be documented.
Question 47
Integration testing is a Black box testing approach.
A
True
B
False
Question 48
Integration testing is also know as end to end testing.
A
False
B
True
Question 48 Explanation: 
Integration and end-to-end testing are different.
Question 49
Bottom up and Topdown are the 2 common approaches for Integration testing.
A
False
B
True
Question 50
Big bang is one of the approaches for Integration testing.
A
False
B
True
Question 51
Sandwitch testing is also one of the Integration testing approaches.
A
False
B
True
Question 52
Defects can be found more easily in Botton up integration testing compared to Top down testing approach.
A
False
B
True
Question 53
Test Cases are not documented for Integration testing.
A
False
B
True
Question 54
Integration test cases cannot be automated.
A
True
B
False
Question 54 Explanation: 
Automating Integration testing is difficult but not impossible.
Question 55
Load Testing is a non-functional test type.
A
True
B
False
Question 56
Load Testing and Stress testing are one and the same.
A
False
B
True
Question 57
Load Testing is done to check response of application under peak load conditions.
A
False
B
True
Question 58
Load Testing allows to determine maximum operating capacity of an application.
A
True
B
False
Question 59
Load Testing helps to identify application performance bottlenecks.
A
True
B
False
Question 60
Stress Testing is a non-functional type of testing.
A
True
B
False
Question 61
Stress Testing helps to determine application behaviour at peak or over peak load conditions.
A
False
B
True
Question 62
Stress Testing helps to determine application upper limits capacity.
A
False
B
True
Question 63
Stress Testing is similar to Load Testing but objectives of both testing types are different.
A
False
B
True
Question 64
Endurance Testing is also known as Soak Testing
A
True
B
False
Question 65
Endurance Testing is also known as Longitivity testing.
A
False
B
True
Question 66
Objective of Endurance Testing is to find performance degradation due to load over longer duration of time.
A
False
B
True
Question 67
Endurance Testing is similar to Load testing but tests done ____________
A
with max load
B
for longer duration
Question 68
Endurance Testing, stress testing and Load testing requires different automation tools.
A
True
B
False
Question 69
Objective of Installation testing is to find issues related to Installation of software.
A
False
B
True
Question 70
Installation/Uninstallation testing is a must for both Off the shelf and web application services.
A
False
B
True
Question 70 Explanation: 
Installation/Uninstallation testing is requried for off the shelf softwares which requires end users require to install the software. Incase of web application services, installation is done by the product development company and end users only use the services they dont install the application on the server.
Question 71
Installation/uninstallation testing will not include partial installation or upgrades as part of test.
A
False
B
True
Question 71 Explanation: 
Partial installation and upgrades are also part of installation/uninstallation testing.
Question 72
Installation/Uninstallation testing can involve testing on various OS and hardwares.
A
False
B
True
Question 73
Objective of recovery testing is to check how an application recovers in an event of failure.
A
False
B
True
Question 74
Recovery Testing is also known as Failover testing.
A
False
B
True
Question 75
Recovery Testing scenarios can involve checking ability of software to recover from OS crashes.
A
False
B
True
Question 76
Recovery Testing scenarios can involve checking ability of software to recover post Hardware failures.
A
True
B
False
Question 77
Recovery Testing scenarios can involve checking ability of software to recover post network outages.
A
False
B
True
Question 78
Alpha Testing is done by end users.
A
False
B
True
Question 79
Alpha Testing is done before product or software is launched.
A
True
B
False
Question 80
Alpha Testing is done at development site.
A
False
B
True
Question 81
Alpha Testing is applicable mostly for Off the shelf softwares.
A
False
B
True
Question 81 Explanation: 
Alpha testing and beta testing is also done for web applications, yahoo and google announced Alpha and beta test phases for their applications in the past.
Question 82
Alpha testing is done after Beta Testing.
A
True
B
False
Question 83
Beta Testing is done by end users.
A
True
B
False
Question 84
Beta Testing is done before product or application is launched.
A
False
B
True
Question 85
Beta Testing is done at development site.
A
False
B
True
Question 86
Beta testing is done after Alpha Testing.
A
True
B
False
Question 87
Ad hoc testing is an informal type of testing.
A
False
B
True
Question 88
Ad hoc testing can find defects that might not have been found by executing test cases.
A
False
B
True
Question 89
Ad hoc testing does not have documented test cases.
A
False
B
True
Question 90
Objectives of Ad hoc testing and exploratory testing are one and the same.
A
True
B
False
Question 91
Objective of Ad hoc testing is to find defects that were not reported so far.
A
False
B
True
Question 92
Ad hoc testing is a Black box testing technique.
A
False
B
True
Question 93
Regression testing is done to determine whether change in code has resulted in new defects.
A
True
B
False
Question 94
Regression test cases are usually not documented.
A
True
B
False
Question 94 Explanation: 
Regression test cases are always documented.
Question 95
Regression tests are intended to find functional and non-functional defects.
A
False
B
True
Question 96
Regression testing is carried out on every build
A
True
B
False
Question 97
Regression tests can be broadly categorized as functional tests and unit tests.
A
True
B
False
Question 98
Another name of Regression test is Retesting.
A
False
B
True
Question 99
Regression tests are a good candidate for automation.
A
False
B
True
Question 100
Number of regression tests for a release depends on the extent of code changes.
A
True
B
False
Once you are finished, click the button below. Any items you have not completed will be marked incorrect. Get Results
There are 100 questions to complete.

Note:
List of objective questions on types of software testing is contributed by Alok Tiwari (new guest writer)

Other Interesting Articles:


Share this article with friends and colleague if you like it OR Share it with your boss if you got bored :-)

5 comments ↓

#1 Rajan on 06.08.12 at 12:32 pm

wow, nice test on types of software testing. my humble request to post such nice test on various other topics, it will be very interesting and useful

#2 Tanveer on 07.23.12 at 11:47 pm

Cool

#3 Balu on 07.27.12 at 6:44 am

Very nice questions.

#4 Ambrene on 09.10.12 at 12:12 am

Hello, I like all articles related to software testing on your site, great job…

#5 chiranjeevi on 03.15.13 at 12:16 pm

very nice and good.. post some more questions to my mail :: mareddyc@gmail.com.
it will be helpfull

Leave a Comment

Comment moderation is enabled. Your comment may take some time to appear.







Page 1 of 11



Software Testing Software > Software Testing Quiz > Types of software testing