Please enable JavaScript.

Coggle requires JavaScript to display documents.

C6 : Test Management (Test Progress Monitoring & Control (Test Metrics…

- - - - Defect based metrics
      - Test case based metrics
      - Test object based metrics
- - - - Risks regarding the achievement of the project objectives
        
        late delivery of the test items to the test team
        
        excessive delays in repairing defects found in testing
    - - Risks regarding the test object (and its usage)
        
        New Technologies used in the product
        
        Tight Schedules,
- - - - Able to test assumptions made by developers
      - Able to see other and different possibilities for defects
    - - Test can be seen as a bottleneck
      - Need high effort for communication
      - Developers can lose responsibility
- - - - to define how the testing will be conducted.
    - - Defines how the organisation will conduct testing
        
        Test Policy
      - Defines how the project will conduct testing
        
        Master Test Plan/ Test Strategy
      - Defines how each level of testing will be conducted
        
        Functional
        Test Plan
        
        System Integration
        Test Plan
        
        UAT Test Plan
    - - Identify the objectives of testing
      - Determine the scope and risks
      - Define the overall testing approach
      - Schedule test activities
      - Assign resources to activities
    - - Define when to start testing
        
        Complete or partially testable code is available.
        
        Requirements are defined and approved.
        
        Availability of sufficient and desired test data.
        
        Test cases are developed and ready.
    - - Define when to stop testing
        
        Deadlines meet or budget depleted.
        
        Execution of all test cases.
        
        All the identified defects are corrected and closed.
        
        No high priority or severity or critical bug has been left out.
  - - - approach
        
        Expert Estimation
        
        Via people in charge of these tasks
        
        Via external experts
        
        Analogy Estimation
        
        based on metrics of previous or similar projects
        
        based on typical values (metric-based approach)
        
        function point count
        
        unit testing done by developers
        
        risk levels of the project
      - factor influence test efforts
        
        Characteristics of the product
        
        Characteristics of the development process
        
        Outcome of testing
- - - - Objectives, scope, schedule, automation tools, resources, risk analysis, test environment, defect management
  - - - Test design techniques
      - Test types
      - Entry & exit criteria
    - - Before code is delivered
    - - After code is delivered
    - - Analytical : risks based, requirement based
      - Model-based: mathematical models
      - Methodical: Checklist
- - - - Severity
        
        potential impact of the incident
        
        Major
        
        Minor
        
        Critical
        
        Fatal
      - Priority
        
        Influence by severity and affect the working status of the system
        
        Urgent/Immediate
        
        HIgh
        
        Medium
        
        Low
      - Status
        
        The current state where handling the incident is at
        
        New
        
        In Progress
        
        Resolved
        
        Closed