1. Test organization
1.1. Degrees of independence
1.1.1. Developers testing their own code
1.1.2. Developers testing their colleagues code
1.1.3. Tester within the development team
1.1.4. Testers not in the same team but within the same organization
1.1.5. Testers from a different organization
1.2. Benefits of independent testing
1.2.1. Independent testers are likely to recognize different kinds of failures compared to developers
1.2.2. independent tester can verify, challenge, or disprove assumptions made by stakeholders
1.2.3. Independent testers of a vendor can report in an upright and objective manner about the system under test without (political) pressure
1.3. Drawbacks of independent testing
1.3.1. Isolation from the development team, may lead to a lack of collaboration
1.3.2. Developers may lose a sense of responsibility for quality
1.3.3. Independent testers may be seen as a bottleneck
1.3.4. Independent testers may lack some important information
1.4. Tasks of test manager
1.4.1. Develop or review a test policy and test strategy
1.4.2. Plan the test activities
1.4.3. Write and update the test plan(s)
1.4.4. Coordinate the test plan(s) with others
1.4.5. Share testing perspectives with other project activities
1.4.6. Initiate test process activities, check the status of exit criteria & facilitate test completion activities
1.4.7. Prepare and deliver test progress reports and test summary reports
1.4.8. Adapt planning based on test results and progress & take actions for test control
1.4.9. Support setting up the defect management system and adequate configuration management of testware
1.4.10. Introduce suitable metrics
1.4.11. Support the selection and implementation of tools
1.4.12. Decide about the implementation of test environment(s)
1.4.13. Promote and advocate the testers, the test team, and the test profession within the organization
1.5. Tasks of tester
1.5.1. Review and contribute to test plans
1.5.2. Analyze, review, and assess test basis
1.5.3. Identify and document test conditions, and capture traceability between test cases, test conditions, and the test basis
1.5.4. Design, set up, and verify test environment(s),
1.5.5. Design and implement test cases and test procedures
1.5.6. Prepare and acquire test data
1.5.7. Create the detailed test execution schedule
1.5.8. Execute tests & document deviations from expected results
1.5.9. Use appropriate tools to facilitate the test process
1.5.10. Automate tests as needed
1.5.11. Evaluate non-functional characteristics
2. Test planning & estimation
2.1. Purpose of test plan
2.1.1. A test plan outlines test activities for development and maintenance projects.
2.2. Test planning activities
2.2.1. Determining the scope, objectives, and risks of testing
2.2.2. Defining the overall approach of testing
2.2.3. Integrating and coordinating the test activities into the SW lifecycle activities
2.2.4. Making decisions about what to test, the people and other resources required
2.2.5. Scheduling of test process activities
2.2.6. Selecting metrics for test monitoring and control
2.2.7. Budgeting for the test activities
2.2.8. Determining the level of detail and structure for test documentation
2.3. Test strategies
2.3.1. Analytical
2.3.1.1. - Based on an analysis of requirements & risks - Risk-Based analysis is an example of an analytical approach
2.3.2. Model-Based
2.3.2.1. - Tests are designed based on some model of some required aspect of the product,
2.3.3. Methodical
2.3.3.1. - Relies on making systematic use of some predefined set of tests or test conditions
2.3.4. Process-compliant
2.3.4.1. - Also called standard-compliant - Involves analyzing, designing, and implementing tests based on external rules and standards
2.3.5. Directed
2.3.5.1. Driven primarily by the advice, guidance, or instructions of stakeholders, business domain experts, or technology experts
2.3.6. Regression-averse
2.3.6.1. - Avoid regression of existing capabilities - Includes reuse of existing testware
2.3.7. Reactive
2.3.7.1. - Testing is reactive to the component or system being tested - Exploratory testing is a common technique employed in reactive strategies.
2.4. Entry criteria
2.4.1. Availability of testable requirements, user stories, and/or models
2.4.2. Availability of test items that have met the exit criteria for any prior test levels
2.4.3. Availability of test environment
2.4.4. Availability of necessary test tools
2.4.5. Availability of test data and other necessary resources
2.5. Exit criteria
2.5.1. Planned tests have been executed
2.5.2. A defined level of coverage have been achieved
2.5.3. The number of unresolved defects is within an agreed limit
2.5.4. The number of estimated remaining defects is sufficiently low
2.5.5. The evaluated levels of reliability, performance efficiency, usability, security, and other relevant quality characteristics are sufficient
2.6. Test Execution Schedule
2.6.1. Once the various test cases and test procedures are produced and assembled into test suites, the test suites can be arranged in a test execution schedule that defines the order in which they are to be run.
2.6.2. Success factors are prioritization, dependencies, confirmation tests, regression tests, and the most efficient sequence for executing the tests.
2.7. Factors that influence the test effort
2.7.1. Product characteristics
2.7.2. Development process characteristics
2.7.3. People characteristics & skills
2.7.4. Test results
2.8. Estimation techniques
2.8.1. Metric-Based
2.8.1.1. estimating the test effort based on metrics of former similar projects, or based on typical values
2.8.2. Expert-Based
2.8.2.1. estimating the test effort based on the experience of the owners of the testing tasks or by experts
3. Test monitoring & control
3.1. Metrics used for testing
3.1.1. Metrics used during or at the end of each testing activity in order to assess: Progress, effectiveness, percentage of work done, test coverage, task completion & cost of testing
3.2. Test reports
3.2.1. Test progress reports
3.2.2. Test Summary/Completion reports
4. Configuration management
4.1. How CM supports testing
5. Risks & testing
5.1. Risk level by likelihood & impact
5.2. Product risk
5.2.1. involves the possibility that a work product may fail to satisfy the legitimate needs of its users and/or stakeholders
5.3. Project risk
5.3.1. involves situations that, should they occur, may have a negative effect on a project's ability to achieve its objectives
5.3.1.1. Project issues
5.3.1.2. Organizational issues
5.3.1.3. Political issues
5.3.1.4. Technical issues
5.3.1.5. Supplier issues
5.4. Risk-Based Testing
5.4.1. Reduce the level of product risk
5.4.2. Involve product risk analysis
5.4.3. Resulting product risk information is used to guide test planning, the specification, preparation and execution of test cases, and test monitoring and control
5.4.4. Analyzing product risks early contributes to the success of a project.