This assessment is intended to assess your knowledge on Types of Testing and Testing Basics.
Should be able to understand a functional specification or requirements document.
Should be able to understand the source code.
Is highly motivated to find faults.
Is creative to find the system’s weaknesses.
Measuring response time
Measuring transaction rates
Recovery testing
Simulating many users
It starts the execution only when the design gets finalized.
It involves simultaneous design of the test and execution.
It starts the execution only when the design gets renewed.
It starts the execution only when the design gets amended.
A black box testing technique used only by developers.
A black box testing technique than can only be used during system testing.
A black box testing technique appropriate to all levels of testing.
A white box testing technique appropriate for component testing.
Missing Statements
Unused Branches
Dead Code
Unused Statement
Error guessing
Walkthrough
Data flow analysis
Inspections
Different Tools to perform Regression Testing.
Exit Criteria.
How many more test cases need to be written
How much regression testing should be done
A high level document describing the principles, approach and major objectives of the organization regarding testing.
A distance set of test activities collected into a manageable phase of a project.
A test environment comprised of stubs and drives needed to conduct a test.
A set of several test cases for a component or system under test.
To know when a specific test has finished its execution.
To ensure that the test case specification is complete.
To know when test planning is complete.
To plan when to stop testing.
Checking that we are building the right system.
Checking that we are building the system right.
Performed by an independent test team.
Making sure that it is what the user really wants.
Number of undetected defects
Number of test cases not yet executed
Total number of defects in the product
Effort required to fix all defects
Module testing
Integration testing
White Box testing
Software testing
Determining the test approach
Preparing test specifications
Evaluating exit criteria and reporting
Measuring and analyzing results
Performed by customers at their own site.
Performed by customers at their software developer’s site.
Performed by an independent test team.
Useful to test bespoke software.
Finding faults in the system.
Ensuring that the system is acceptable to all users.
Testing the system with other systems.
Testing for a business perspective
Equivalence partitioning.
State transition testing.
Linear code sequence and jump.
Syntax testing.
Re-testing is running a test again; regression testing looks for unexpected side effects.
Re-testing looks for unexpected side effects; regression testing is repeating those tests.
Re-testing is done after faults are fixed; regression testing is done earlier.
Re-testing uses different environments, regression testing uses the same environment.
Beta
Gamma
Alpha
None of the above
Test implementation and execution.
Test planning and control.
Test analysis and design.
Evaluating exit criteria and reporting.
Code reviews.
Code inspections.
A coverage tool.
A static analysis tool.
Wait!
Here's an interesting quiz for you.