Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 5 - Coggle Diagram

- - - - Understanding the pupose of testing
      - The select strategies which are appropriate to the purpose of testing
    - - First, writing a test plan guides our thinking
      - Writing a test plan forces us to confront the challenges that awaits us and focus our thinking on importaant topics
      - Test plan itself serves as a vehicle for communicating with other members of the project team: testers, peers, managers and
        other stakeholders
  - - - Methodical
      - Process or standard complant
      - Model-based
      - Dynamic
      - Analytical
      - Consultative or directed
      - Regression-averse
- - - - At the outset of project, test leaders, in collaboration with other stakeholders, devise the test objectives, organizational test policies, test strategies and test plans
      - As test excution near, they make sure the test environment is put into place before test execution and managed during test execution
      - During test execution and as the project winds down, they write summary reports on test status
      - Planning, monitoring and control
  - - - As test execution begins, the number of testers often increases, stating with the work required to implement tests in the test environment
      - Executing and loggin the tests, evaluate the results and document problems found
      - In the planning and preparation phases of the testing, testers should review and contribute to test plans, as well as analyzing, reviewing and assessing requirements and design specification
      - Throughout the testing life cycle, they review each other's work, including test specifications, defect reports and test results
  - - - Pros
        
        An independent tester brings a different set of assumptions to testing and to review -> help expose hidden defects and problems related to group's thinking
        
        An independent test team often has a seperate budget -> help ensure the proper level of money is spent on training, test tools,..
      - Cons
        
        It's possible for the test team and the test team to become isolated
        
        Some programmers abdicate their responsibility for quality
- - - - Comparing an observed problem against other test result or known defects
      - Use a carerful, attentive approach to run the tests
      - Clear and unambigous
    - - Describe as much details as possible
      - Describe and evaluate damage caused by the incidents
      - A summery that provides enough of information about the problem
    - - Provide information about the observed incidents
      - Support analysis
      - Test improvement
- - - - Dicuss
        
        the object of testing and whether they were achieved
        
        the test strategy followed and how well it worked
        
        important event that occured during the test
        
        the overall effectiveness of the test effort
  - - - include orther common metric
        
        The extent of test coverage archieved, measured against requirements, test , code, configuration or orther area of interst
        
        The status of testing compared to various test mile stone
        
        The extent of completion of test environment preparation
        
        The economics of tesing , such as costs and benefits of test execution of finding next defect
    - - Gathering the data for using in estimating future test effort
      - Feedback on how the test work is going
      - Guide and improve the testing and the project
      - Provide the project team with visibility test result
      - Measure the status of testing , test coverage, test items against exit criteria
    - - Regulatory requirements
      - time money constrains
      - The need and goal of the project
      - orther factors
      - The preferences of tester and stakeholder
- - - - Organized strategy to mitigate product risk
        
        Mitigation: Reduce likelihood
        
        Contigency: Prepare a backup plan to reduce risk impact
      - Product risk analysis
        
        Process
        
        Structure potential risk
        
        Revise part 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
        
        Techniques
        
        Reading documents
        
        Discussion and consultance
        
        Brainstorming