Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Testing Week04 (Test Plan, Test Case) - Coggle Diagram

- - - - 1.1 Scope
        
        1.1.1 In Scope
        Scope defines the features, functional or non-functional requirements of the software that will be tested
        
        1.1.2 Out Scope
        Out Of Scope defines the features, functional or non-functional requirements of the software that will NOT be tested
      - 1.2 Quality Objective
        Here make a mention of the overall objective that you plan to achive with your manual testing and automation testing.
        
        Ensure the Application Under Test conforms to functional and non-functional requirements
        
        Ensure the AUT meets the quality specifications defined by the client
        
        Bugs/issues are identified and fixed before go live
      - 1.3 Roles and Responsibilities
        Detail description of the Roles and responsibilities of different team members
        
        QA Analyst 1
        
        Test Manager 2
        
        Configuration Manager 3
        
        Developers 4
        
        Installation Team 5
    - - 2.2 Test Level
        
        Test Levels define the Types of Testing to be executed on the Application Under Test (AUT). The Testing Levels primarily depends on the scope of the project, time and budget constraints.
      - 2.1 Overview
        Mention the reason of adopting a particular test methodology for the project. The test methodology selected for the project could be
        
        WaterFall 1
        
        Agile 2
        
        Iterative 3
        
        Extreme Programming 4
      - 2.3 Bug Triage
        
        To define the type of resolution for each bug
        
        To prioritize bugs and determine a schedule for all “To Be Fixed Bugs’.
      - 2.4 Suspension Criteria and Resumption Requirements
        
        Suspension criteria define the criteria to be used to suspend all or part of the testing procedure while Resumption criteria determine when testing can resume after it has been suspended
      - 2.5) Test Completeness
        Here you define the criterias that will deem your testing complete.
    - - Test Plan
      - Test Cases
      - Requirement Traceability Matrix
      - Bug Reports
      - Test Strategy
      - Test Metrics
      - Customer Sign Off
    - - 4.1 Testing Tools
        
        Requirements Tracking Tool
        
        Bug Tracking Tool
        
        Automation Tools
      - 4.2 Test Environment
        It mentions the minimum hardware requirements that will be used to test the Application.
    - - Make a mention of any terms or acronyms used in the project
      - Example:
        
        API: Application Program Interface
        
        AUT: Application Under Test
- - - - Work Breakdown Structure
      - 3-Point Software Testing Estimation Technique
      - Wideband Delphi technique
      - Function Point/Testing Point Analysis
      - Use – Case Point Method
      - Percentage distribution
      - Ad-hoc method
    - - Step1) Divide the whole project task into subtasks
        
        1
        
        Analyze software requirement specification
        
        2
        
        Create the Test Specification
        
        3
        
        Execute the test cases
        
        4
        
        Report the defects
      - Step 2) Allocate each task to team member
        
        Analyze software requirement specification
        
        All the members
        
        Create the test specification
        
        Tester/Test Analyst
        
        Build up the test environment
        
        Test Administrator
        
        Execute the test cases
        
        Tester, Test Administrator
        
        Report defects
        
        Tester
      - Step 3) Effort Estimation For Tasks
        
        Method 1) Function Point Method
        
        1
        
        Estimate size for the task
        
        2
        
        Estimate duration for the task
        
        Total Effort = Total Function Points * stimate defined per Function Points
        
        3
        
        Estimate the cost for the tasks
        
        Method 2) Three Point Estimation
        
        The best case
        
        The most likely
        
        The worst case
      - Step 4) Validate the estimation
- - - - Analyze the product
        
        Who will use the website?
        
        What is it used for?
        
        How will it work?
        
        What are software/ hardware the product uses?
    - - Develop Test Strategy
        
        Define Scope of Testing
        
        Precise customer requirement
        
        Project Budget
        
        Product Specification
        
        Skills & talent of your test team
        
        Problem Scenario
        
        In-scope items: Functional Testing, Api Testing
        
        Out of scope items: Database Testing, hardware & any other external interfaces
        
        Identify Testing Type
        
        A) Unit Testing
        
        B) API Testing
        
        C) Integration Testing
        
        D) System Testing
        
        E) Install/Uninstall Testing
        
        F) Agile testing
        
        Document Risk & Issues
        
        Create Test Logistics
        
        Who will test?
        
        Ability to understand customers point of view
        
        Strong desire for quality
        
        Attention to detail
        
        Good cooperation
        
        When will the test occur?
        
        Test specs and Requirement document
        
        Human resources
        
        Test environment
    - - Define Test Objective
        
        List all the software features (functionality, performance, GUI…) which may need to test.
        
        Define the target or the goal of the test based on above features
    - - Define Test Criteria
        
        Suspension Criteria
        
        the active test cycle will be suspended until the criteria are resolved
        
        Exit Criteria
        
        Run rate is ratio between number test cases executed/total test cases of test specification
        
        Pass rate is ratio between numbers test cases passed / test cases executed
    - - Resource Planning
        
        Human Resource
        
        Test Manager
        
        Tester
        
        Developer in Test
        
        Test Administrator
        
        SQA members
        
        System Resource
        
        Server
        
        Test tool
        
        Network
        
        Computer
    - - Plan Test Environment
        
        What is the maximum user connection which this website can handle at the same time?
        
        What are hardware/software requirements to install this website?
        
        Does the user’s computer need any particular setting to browse the website?
    - - Schedule & Estimation
    - - Test Deliverables
        
        before testing
        
        Test plans document.
        
        Test cases documents
        
        Test Design specifications.
        
        during testing
        
        Test Scripts
        
        Simulators.
        
        Test Data
        
        Test Traceability Matrix
        
        Error logs and execution logs.
        
        after testing
        
        Test Results/reports
        
        Defect Report
        
        Installation/ Test procedures guidelines
        
        Release notes
- - - - Test case ID:
        Each test case should be represented by a unique ID. To indicate test types follow some convention like “TC_UI_1” indicating “User Interface Test Case#1.”
    - - Test Priority: Low, medium, high
    - - Name of the Module: Determine the name of the main module or sub-module being tested
    - - Test Designed by: Tester’s Name
    - - Date of test designed: Date when test was designed
    - - Date when test was designed: Who executed the test- tester
    - - Date of the Test Execution: Date when test needs to be executed
    - - Name or Test Title: Title of the test case
    - - Description/Summary of Test:
        Determine the summary or test purpose in brief
    - - Pre-condition:
        Any requirement that needs to be done before execution of this test case. To execute this test case list all pre-conditions
    - - Dependencies:
        Determine any dependencies on test requirements or other test cases
    - - Test Steps
        Mention all the test steps in detail and write in the order in which it requires to be executed.
    - - Test Data:
        Use of test data as an input for the test case
    - - Expected Results:
        Mention the expected result including error or message that should appear on screen
    - - Post-Condition:
        What would be the state of the system after running the test case?
    - - Actual Result: After test execution, actual test result should be filled
    - - Status (Fail/Pass):
        Mark this field as failed, if actual result is not as per the estimated result
    - - Notes:
        If there are some special condition which is left in above field
- - - - Read the Requirement Documents like BRS, SRS, FRS, of the System Under Test (SUT). You could also refer uses cases, books, manuals, etc. of the application to be tested.
    - - For each requirement, figure out possible users actions and objectives. Determine the technical aspects of the requirement. Ascertain possible scenarios of system abuse and evaluate users with hacker’s mindset.
    - - After reading the Requirements Document and doing your due Analysis, list out different test scenarios that verify each feature of the software.
    - - Once have listed all possible Test Scenarios, a Traceability Matrix is created to verify that each & every requirement has a corresponding Test Scenario
    - - The scenarios created are reviewed by your supervisor. Later, they are also reviewed by other Stakeholders in the project.
- - - - A test case description to explain the scenario would be
    - - Prepare test data
    - - To execute a test case, perform a specific set of actions on the AUT
    - - Check behavior of the AUT for an expected result
    - - Specify the pre-condition and post-condition
  - - - Test management tools are the automation tools that help to manage and maintain the Test Cases.
    - - For documenting Test Cases
      - Execute the Test Case and Record the results
      - Automate the Defect Tracking
      - Traceability
      - Protecting Test Cases
    - - Quality Center
      - Jira
- - - - Testing data may contain invalid parameter types used to call different methods
      - Testing data may consist in invalid combinations of arguments which are used to call the program’s methods