ISTQB

The main points of this activity are:1) Reviewing requirements, architecture, design, interface specifications and other parts, which collectively comprise the test basis.2) Analyzing test items, the specification, behavior and structure to identify test conditions and test data required.3) Designing the tests, including assigning priority.4) Determining whether the requirements and the system are testable.5) Detailing what the test environment should look like, and whether there are any infrastructure and tools required.6) Highlighting the test data required for the test conditions and test cases.7) Creating bi-directional traceability between test basis and test cases.

Test planning has following major tasks: i. To determine the scope and risks and identify the objectives of testing. ii. To determine the test approach. iii. To implement the test policy and/or the test strategy. (Test strategy is an outline that describes the testing portion of the software development cycle. It is created to inform PM, testers and developers about some key issues of the testing process. This includes the testing objectives, method of testing, total time and resources required for the project and the testing environments.). iv. To determine the required test resources like people, test environments, PCs, etc. v. To schedule test analysis and design tasks, test implementation, execution and evaluation. vi. To determine the Exit criteria we need to set criteria such as Coverage criteria. (Coverage criteria are the percentage of statements in the software that must be executed during testing. This will help us track whether we are completing test activities correctly. They will show us which tasks and checks we must complete for a particular level of testing before we can say that testing is finished.)

Test control has the following major tasks:

1. To measure and analyze the results of reviews and testing.
2. To monitor and document progress, test coverage and exit criteria.
3. To provide information on testing.
4. To initiate corrective actions.
5. To make decisions.

Test implementation and execution has the following major tasks:

1. Developing, implementing and prioritizing test cases.
2. Developing and prioritizing test procedures, creating test data and, optionally, preparing test harnesses and writing automated test scripts.
3. Creating test suites from the test procedures for efficient test execution.
4. Verifying that the test environment has been set up correctly.
5. Executing test procedures either manually or by using test execution tools, according to the planned sequence.
6. Logging the outcome of test execution and recording the identities and versions of the software under test, test tools and testware.
7. Comparing actual results with expected results.
8. Reporting discrepancies as incidents and analyzing them in order to establish their cause (e.g. a defect in the code, in specified test data, in the test document, or a mistake in the way the test was executed).
9. Repeating test activities as a result of action taken for each discrepancy. For example, reexecution of a test that previously failed in order to confirm a fix (confirmation testing), execution of a corrected test and/or execution of tests in order to ensure that defects have not been introduced in unchanged areas of the software or that defect fixing did not uncover other defects (regression testing)

Evaluating exit criteria has the following major tasks:

1. Checking test logs against the exit criteria specified in test planning.
2. Assessing if more tests are needed or if the exit criteria specified should be changed.
3. Writing a test summary report for stakeholders.

Test implementation and execution

Test implementation and execution

Test implementation and execution

Test implementation and execution

Test implementation and execution

Test implementation and execution

Test implementation and execution

Test implementation and execution

Test implementation and execution

Evaluating exit criteria and reporting