Skip to content

Latest commit

 

History

History
118 lines (112 loc) · 4.92 KB

6. QA Documents.md

File metadata and controls

118 lines (112 loc) · 4.92 KB
Raw

Documents in QA

  1. Requirement Traceability Matrix (RTM):
    • This is often created early in the process to map requirements to test cases, ensuring comprehensive test coverage.
  2. Test Plan:
    • A test plan is developed to outline the overall testing strategy, scope, objectives, resources, and schedule for the testing process.
  3. Test Suite:
    • Test suites are organized based on the test plan and include a collection of test cases that align with specific features or functionalities.
  4. Test Cases:
    • Detailed test cases are created within each test suite, describing step-by-step instructions for testing different aspects of the software.
      • Test Case Should be,
        1. Keep it simple.
        2. Ensure 100% coverage.
        3. Avoid test case repetition.
        4. Test cases must be readily identifiable.
        5. Test cases should be transparent and straightforward.

Simple Test Case Format

Test Case ID Test Scenario Test Data Expected Output Actual Output Comments

Sample Login Test Case

Test Scenario ID TS001
Test Case ID TC001
Test Case Description Verify User Login
Test Priority High
Pre-requisites User account exists
Post-requisites User is logged in
NO Actions Inputs Expected Output Actual Output Test Results Test Comment
1 1. Navigate to login page
2. Enter username and password
3. Click 'Login' button 		Username, Password Successful login message Welcome message Pass Login functionality works as expected.
  1. Test Scenarios:
    • Test scenarios can be derived from the test cases and provide high-level descriptions of interactions and workflows to be tested.
  2. Test Bed:
    • The test bed is set up to create an environment suitable for executing the tests outlined in the test cases.
    • Execution of Tests - Testers execute the test cases in the designated test bed to identify defects and verify the software's functionality.
  3. Bug Report:
    • When defects are identified during testing, bug reports (or defect reports) are created to document the issues found, including their details and severity.
  4. Test Metrics:
    • Throughout the testing process, various metrics can be collected to assess the quality and progress of testing activities.
  5. Test Summary Reports:
    • Once testing is completed, a test summary report is generated to provide an overview of the testing activities, including test execution results, defect details, and assessment of software quality.
  6. Release Notes:
    • After testing and bug fixing are complete, release notes are prepared to communicate the changes, enhancements, and bug fixes made in the software release.
  7. Test Data:
    • This document outlines the data sets and inputs that will be used during testing. It ensures that the tests cover a variety of scenarios and edge cases.
  8. Test Environment Setup:
    • This document provides instructions for setting up the test environment, including hardware, software, configurations, and dependencies required for testing.
    • Different types of Test environments in Software projects:
      • Development Environment: Used for writing and testing code, typically on a developer's local machine.
      • Integration Environment: Integrates different software components, ensures they work together.
      • Staging Environment: Pre-production environment, mimics production for final testing.
      • User Acceptance Testing (UAT) Environment: End-users test software for requirements, mirrors production closely.
      • Production Environment: Live environment for end-users, where software is used as intended.
      • Performance Testing Environment: Tests software under load, matches production hardware.
      • Security Testing Environment: Focuses on software security, uses security tools and configurations.
      • Sandbox or Experimental Environment: For experimental and exploratory testing, allows trying new ideas safely.
  9. Test Execution Logs:
    • These logs record the details of test execution, including test case IDs, execution dates, results, and any deviations from expected outcomes.

Please note that the exact order may vary based on the project's needs and the specific testing methodology being used. Additionally, some of these documents might be created or updated concurrently as the testing process unfolds.