Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter5 - Coggle Diagram

- - - - Writing a test plan forces us to confront the challenges that await us and focus our thinking on important topics
      - itself serve as vehicles for communicating with other members of the project team, testers, peers, managers and other stakeholders
      - First, writing a test plan guides our thinking.
    - - Understanding the purpose of testing
      - Then select strategies which are appropriate to the purpose of testing
  - - - -Analytical.
        -Model-based.
        -Methodical.
        -Process- or standard-compliant.
        -Dynamic.
        -Consultative or directed.
        -Regression-averse.
- - - - A Summary
        
        Provide enough details of the problem
      - Incident description
        
        Describe as much details as posible
      - Impact
        
        Describe and evalute damage cause by the incident
    - - Provide information about the observed incidents
      - Support analysis
      - Test improvement
    - - Use a careful, attentive approach to running your tests
      - Comparing an observed problem
        against other test results or known defects
      - Clear and unambiguous
- - - - At the outset of the project, test leaders, in collaboration with the other stakeholders, devise the test objectives, organizational test policies (if not already in place), test strategies and test plans.
      - As test execution comes near, they make sure the test environment is put into place before test execution and managed during test execution
      - Test leaders tend to be involved in the planning, monitoring, and control of the testing activities and task
      - During test execution and as the project winds down, they write
        summary reports on test status
  - - - Cons
        
        -It's possible for the testers and the test team to become isolated
        
        Some programmers abdicate their responsibility for quality
      - pros
        
        An independent tester brings a different set of assumptions to testing and to reviews
        -> helps expose hidden defects and problems related to the group's way of thinking.
        
        An independent test team often has a separate budget -> helps ensure the proper level of money is spent on tester training, testing tools, test equipment, and so forth
- - - - Organized strategy to mitigate product risk
        
        Mitigation
        
        Reduce likelihood
        
        Contingency
        
        Prepare a backup plan to reduce risk impact
      - Product risk analysis
        
        Techniques
        
        Reading documents
        
        Discussion and consultance
        
        Brainstorming
        
        Process
        
        Structure potential risk
        
        Revise past risk + test case + bugs
        
        Identify + Rate risk items
        
        Decide risk-mitigation options considering likelihood and impact
        
        Note
        
        Follow up at model milestone
        
        Revisit analysis while testing
  - - - Reduce likelihood or Accept risk
    - - Do nothings and accept bugs as a part of the system (low impact bugs)
- - - - Guide and improve the testing and the project
      - Provide the project team with visibility about the test results
      - Feedback on how the testing work is
        going
      - Measure the status of the testing, test coverage and test items against the exit criteria
      - Gather data for use in estimating future test efforts
    - - include other common metrics
        
        The economics of testing, such as the costs and benefits of continuing test execution in terms of finding the next defect or running the next test.
        
        The status of the testing (including analysis, design and implementation) compared to various test milestones
        
        The extent of test coverage achieved, measured against requirements, risks, code, configurations or other areas of interest
        
        The extent of completion of test environment preparation
    - - regulatory requirements
      - time and money constraints
      - the needs and goals of the
        project
      - other factors.
      - the preferences of the testers and stakeholders
  - - - Discuss
        
        the test strategy followed and how well it worked
        
        the overall effectiveness of the
        test effort
        
        the objectives of testing and whether they were achieved
        
        important events (especially problematic ones) that occurred
        during testing