Manual testing Online Test Series 1, mock test, quiz, exam questions

Unit Testing: Unit testing is performed by the developer to verify the source code of all individual units or module of the application.
Integration Testing: Integration testing is performed by the developer or tester. It is used to verify all modules or units after combining with each other.
System Testing: System testing is performed by the testing team to verify that the system or software meets its specified requirement or not.
So, It is clearly defines that first we have to test all unit modules, then combine all modules and perform integration testing after that we can perform system testing for requirement verification.
Therefore, option A is correct.

Severity: Severity is used to define the impact of the bug on the functionality of the system or system.
Priority: Priority term is used to define the impact of the bug on the client business.
If the application doesn’t allow or work on customer expected configuration is an example of high severity and low priority because this defect does not impact on the client business but its impact on the functionality or GUI of the system so its severity is high.

Therefore, option A is a correct answer.

Statement coverage: statement coverage is used to calculate the coverage of the statements and for identifying all true condition and the conditions should be executed at least one time.

Decision Coverage: Decision coverage statement is used to calculate decision coverage and to identify all statements of decision condition and should be executed at least once.
Cause and effect coverage: Cause and effect coverage term is not used in white box testing.

Multiple condition coverage: It is used to evaluate all the combination of condition.

Therefore, Cause and effect coverage is correct answer.

Drivers are utilized in Bottom-up (Integration) testing where it calls a components to be tested and in Top-down approach stubs are utilized .

Pesticide Paradox Principle: If we use same test cases for testing the application or program, then it will not be useful for finding any new defect. To overcome this problem we need to be regularly review and revise the test cases, this is known as the pesticide paradox principle.
Therefore, Option D is correct.

Iterative model is also known as incremental model. In iterative model the delivery of software is released in multiple builds, version by version.
RAD Model: RAD (Rapid Application Development model). It is a type of incremental model that develops all components parallel and then assembles all the components into a working system.
Spiral model: Spiral model is a combination of iterative development process model and sequential linear development model
Therefore, V model is not related to the iterative model.

Focus Testing: Focus testing is a kind of usability testing. It is performed by the testing team to test the movement of mouse courser for focus and unfocused functionality of the system.
Therefore, option C is a correct answer.

Functional Error: If any error occurrs in the functionality of the application or system, that type of error is known as functional error.
Structural Error: If any error occurrs in the internal structure or code of the system, that kind of defect is known as structural error.
URL Error: If we are not able to access the web site due to error in DNA, Spelling mistake in URL, this type of error is known as URL error.
Therefore, none of these is correct answer.

Masked Defect: Masked defect is an undetected defect that is prevented by the other defect.
Latent Defect: Latent Defect is also known as hidden defect. It is a kind of defect that is found after the delivery of the application because the condition that is required to invoke the defect is not meet.
Therefore, Latent Defect is correct answer.

Fuzz Testing: Fuzz testing is a Data Driven testing that is used to test the application by using invalid or random data as input value for the application.
Active Testing: Active testing is used to evaluate the result of execution by using test data values.

Passive Testing: Passive testing is used to analyze the result of the application without using any test data value.
Fault injection testing: It is performed by QA team for analyzing the system behavior when any exception is occurring.

Therefore, Fault injection testing is correct answer.

I think answer should be (iv) option “All of these”. Because Stress testing means “Testing beyond Max operational capacity to the point from where performance goes down.”
Beyond Normal operational capacity to max operational capacity is Load testing.
and these two type of testing are the part of Performance testing.

Because smoke is nothing but testing the testablity of a application where as sanity testing is testing the features of that application i.e by just opening a application we can perform smoke testing where there it is “opening” or not , on the other side we can perform sanity testing by clicking on the “options” of the opened application .So smoke test comes to action first then sanity.

why because when ever first module comes we test it, if we find any defect then developer fix it and sending new module to testing team so we cant perform regression testing on first module…

we can perform retesting on first module.. how? because retesting means testing whether the bug fixed or not and also testing a functionallity with multiple set of input data so retesting we be done on first build also

so correct answer is REGRESSION TESTING

Sanity Testing: Sanity Testing is a surface level testing that is performed by QA team. It is a subset of regression testing that follows narrow and deep approach with detailed testing to verify the build after performing some changes in code or adding new functionality. It is typically non-scripted and cursory testing to verify software application is working as per the client requirement.
Therefore, option D is correct.

Bottom up integration testing: In the bottom up technique, first we test the sub module then integrate that module and perform the testing. So that why it is more easy to find defect
Top down integration testing: In this technique, first we test the main module and then it divides into 2 or more sub module. In this first we perform integration testing and then unit testing.
Big bang testing: In the big bang technique, first we assemble all the components and then start the testing of application.
Sandwich integration testing: In this technique we divide the overall system in 3 layers and apply different technique in all layers, so some time it is difficult to understand the flow of the functionality.
Therefore, option A is the correct answer.

Unit testing: Unit testing is a white box testing technique that is performed by the developers. It is used to evaluate or verify the source code of all individual units of application is fit for use. The objective of performing unit testing is finding a defect or problem early in the development life cycle, but it doesn’t mean we can catch every error in the program.
Therefore, option A is correct answer.

Vuluerability Testing: Vuluerability Testing is a kind of security testing that is used to prevent the problems which may affect the application integrity and stability. It is performed by the testing team.

Ramp Testing: Ramp testing is performed by testing team that is used to evaluate the system behavior by raising input values continuously.

Penetration Testing: Penetration testing is a kind of security testing that is used to evaluate the security of the application or system.

Fuzz Testing: Fuzz testing is a Data Driven testing that is used to test the application by using invalid or random data as input value for the application. It is performed by the testing team.

Therefore, Vuluerability Testing is a correct answer.

Retesting: Retesting is also known as confirmation testing. It is performed by the tester to verify that the defect or bug has been successfully removed.
Regression Testing: Regression testing is performed after the fixing defects to ensure the change code has not affected the unchanged area of build.
Therefore, option A is correct.

When expected results are specified in advance those are most useful for a tester and developer.