Tag: testing

Black box testing is when we do not have knowledge of testing and in white box testing we have knowledge of testing.

Black box testing is when we do not know the functionality and in white box testing we know the functionality.

Black box testing is when we do not know code used and in white box testing we know the code used.

Black box testing is when we test application randomly and in white box testing we test application using proper test strategy.

Testing that the system functions with other systems

Testing that the components that comprise the system function together

Testing the end to end functionality of the system as a whole

Testing the system performs functions within specified response times

Re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects

Re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed

Re-testing is done after faults are fixed; regression testing is done earlier

Re-testing is done by developers; regression testing is done by independent testers

All the planned tests have been run

Time has run out

All faults have been fixed correctly

Both 1 and 3

It depends on the risks for the system being tested

Parallel testing is a type of testing where the tester reconciles the output of the new system to the output of the current system, in order to verify the new system operates correctly.

Two people testing an application on same machine.

Testing one functionality simultaneously on two different machine having same hardware configuration.

Testing two different functionality simultaneously.

Interoperability (compatibility) testing, reliability testing, performance testing

System testing, performance testing

Load testing, stress testing, component testing, portability testing

Testing various configurations, beta testing, load testing

Number of detected defects, testing cost

Number of residual defects in the test object.

Percentage of completed tasks in the preparation of test environment; test cases prepared

Number of test cases run / not run; test cases passed / failed

State transition testing, code testing, agile testing

Equivalence partitioning, state transition testing, decision table testing

System testing, acceptance testing, equivalence partitioning

System integration testing, system testing, decision table testing

The test object, the test material and the test environment

The problem reports and the test material

Only the test object. The test cases need to be adapted during agile testing

The test object and the test material

Because the tools for automated testing require too much effort for learning

Because the maintenance of the test system is difficult

Because the test robot tools are restricted in their ability to recognize outputs

Because the test robot needs to be supported by a test management.