Test Process

Get Started. It's Free
or sign up with your email address
Rocket clouds
Test Process by Mind Map: Test Process

1. 3. Implementation

1.1. Document

1.1.1. output

1.1.1.1. T.Case Specification

1.1.2. input

1.1.2.1. T. Design Specification

1.2. Activity:

1.2.1. Forming test execution schedule.

1.2.2. Creating and finalizing test data

1.2.3. Prioritizing test cases

1.2.4. Organazing test into execution order

1.2.5. Verifying the test environment

1.2.6. Creating test suites

1.2.7. Defining test cases

1.3. Definition:

1.3.1. The process of developing and prioritizing test procedures, creating test data and ,optionally, preparing test harnesses and writing automated test scripts.

2. 2. Analysis & Design

2.1. Doc. Analysis

2.1.1. output

2.1.1.1. T. Condition Matrix

2.1.2. input

2.1.2.1. T. Basis

2.1.2.2. T. Plan

2.2. Activity in analysis

2.2.1. Evaluating testability; Identifying the test objects and conditions

2.2.2. Design documents

2.2.3. Reviewing requirements, architecture, design documents

2.3. Doc. Design

2.3.1. output

2.3.1.1. T. Design Specification

2.3.2. input

2.3.2.1. T. Condition Matrix

2.3.2.2. T. Plan

2.3.2.3. T. Basis

2.4. Activity in design

2.4.1. Test data creation

2.4.2. Required infrastructure and tools

2.4.3. Test case design techniques;

2.4.4. Determine low-level or high-level test cases are most appropriate

2.4.5. design test based on the objects

2.5. Definition of Analysis&Design

2.5.1. General testing objectives are transformed into clear test conditions and test designs.The aplication should be analysed in detail from both a user's perspective, and rom a technical stand-point.

3. 4. Execution

3.1. Document

3.1.1. output

3.1.1.1. Test Item Transmittal Report

3.1.1.2. T. Log

3.1.2. input

3.1.2.1. T. Case Specification

3.2. Activity:

3.2.1. Relevant and Valid application requirements

3.2.2. Regression list?

3.2.3. If the defect lies with the software then complete details of the defect , should be passed to the development team for fixing, and again it should be re-tested

3.2.4. Testers should be aware of the possibility that the observed results could be due to an incorrect test

3.2.4.1. If its incorrect , it should be corrected and re-run

3.2.5. Changes in the test basis and the test object can render a test case incorrect even after the test has been run successfully many times

3.2.6. Reporting

3.2.7. Expected and actual results do not match

3.2.7.1. Ensure the test is right: refer back from the test data to the test conditions, documentation should be evaluated, refetence from the test data to the test conditionsto the source documentation.

3.2.7.2. Causes: Defects in the software, in the test data, in the test environment, in the requierment specifications

3.2.8. Comparing actual results with expected results - pass or fail

3.2.9. Execution of a corrected test to ensure that defects have not been introduced in unchanged areas

3.2.10. Re-execution of the test that previously faild in order to confirm a fix

3.2.11. Record the result of the test

3.2.12. Executing test cases manually or by tools

3.3. Definition

3.3.1. The process of running a test on the component or system under test, producing actual results

4. 1. Planning

4.1. Documents

4.1.1. output

4.1.1.1. T. Plan

4.1.2. input

4.1.2.1. T. Basis

4.2. Activity

4.2.1. Match the testing with the life cycle.

4.2.2. Prepare and review documents

4.2.3. resources and schedule

4.2.4. SUT

4.2.5. Test strategy

4.3. Definition:

4.3.1. The activity of establishing or updating a test plan.