Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 5 - Coggle Diagram

- - - - writing a test plan guides our thinking
      - forces us to confront the challenges that await us and focus our thinking on important topics
      - using template when writing test plans helps remember the important challenge
      - the test planning process and the plan itself serve as vehicles for communicating with other members of the project's team
      - manage change
      - gives baseline against which to measure such revisions and changes
      - keep testing aligned with project needs
    - - a good test plan is kept short and focused
      - in terms of overall organization needs, the purpose is to referred to variously as the test team's mission or the organization's testing policy
      - in terms of specific project, answer the questions
        
        What is in scope and what is out of scope for this testing effort?
        
        What are the test objectives
        
        What are the important project and product risks?
        
        What constraints affect testing
        
        What is most critical for this product and project?
        
        Which aspects of the product are more (or less) testable?
        
        What should be the overall test execution schedule and how should we decide the order in which to run specific tests?
      - in addition, you need to
        
        decide how to split the testing work into various levels
        
        decide how to best fit your testing work in the level you are responsible for with the testing work done in those other level
        
        reduce gaps and overlap between levels
        
        coordinate between the levels
      - you should plan to integrate and coordinate all the testing work to be done with the rest of the project
      - the entire testing process need to document
      - think about what would be true about the project when the project was ready to start executing test. Some typical factors for criteria
        
        acquisition and supply
        
        test items
        
        defects
        
        tests
        
        coverage
        
        quality
        
        money
        
        risk
      - a successful project is a balance of quality, budget, schedule and feature considerations
  - - - estimate the tasks involve with running a performance test
      - how long those tasks will take
      - how many times you'll need to run the performance tests
    - - estimate task involves
    - - estimate task involves
    - - estimate time required to draft, review and finalize a performance test plane
  - - - process maturity
  - - - analytical
      - model-based
      - methodical
      - process-or standard-compliant
      - dynamic
      - consultative or directed
      - regression-averse
    - - risks
      - skills
      - objectives
      - regulations
      - product
      - business
- - - - Communication problems
      - feelings of alienation and antipathy
      - lack of identification with and support for the project goals
      - spontaneous blame
      - political backstabbing
    - - failure of the test manager to effectively manage risks of independence
      - testers take to acting as enforcers of process or as auditors without a proper management mandate and support
      - it's important for testers and test manager to understand the mission they serve and why the organization wants an independent test team
    - - project
      - application domain
      - levels of risk
  - - - estimate the testing to be done
      - negotiate with management to acquire the necessary resources
      - recognize when test automation is appropriate
      - plan the effort, select tools
      - ensure training of the team
      - as test execution comes near, they make sure test environment is put into place before test execution and managed during test execution
  - - - application or business domain: understand the intended behavior, the problem the system will solve
      - technology: aware of issues, limitations and capabilities of the chosen implementation technology
      - testing
- - - - give the team and the test manager feedback on how the testing work is going
      - provide the project team with visibility about the test results
      - measure the status of the testing, test coverage and test items against the exit criteria
      - gather data for use in estimating future test effort
    - - The extent of completion of test environment preparation;
      - The extent of test coverage achieved, measured against requirements, risks, code, configurations or other areas of interest
      - The status of the testing compared to various test milestones
      - 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
  - - - How will you assess the adequacy of the test objectives for a given test level and whether those objectives were achieved?
      - How will you assess the adequacy of the test approaches taken and whether they support the achievement of the project's testing goals?
      - How will you assess the effectiveness of the testing with respect to these objectives and approaches?