Tell about the testing documentation used in the project.
sobes.tech AI
Answer from AI
The following types of test documentation were actively used on the project:
-
Test Plan: Defined the scope of testing, approach, resources, schedule, and readiness criteria. Coordinated with stakeholders.
-
Test Cases: Described specific steps to verify certain functionality, expected results, and preconditions. Stored in a Test Management System.
Example of a test case structure:
- Test case ID
- Test case name
- Priority
- Type of testing (Functional, Regression, etc.)
- Preconditions
- Execution steps
- Expected result
- Actual result (in case of defect detection)
-
Checklists: Used for less formal, quick walkthroughs of basic functionality or when time was limited. Often used for exploratory testing.
-
Defect Reports: Described identified defects, including reproduction steps, actual and expected results, impact on the system, and priority/severity. Logged in a bug-tracking system.
Example of a defect report structure:
- Defect ID
- Defect name
- Status
- Priority
- Severity
- Creation/update date
- Author
- Software version where the defect was found
- Reproduction steps
- Actual result
- Expected result
- Attachments (logs, screenshots)
-
Traceability Matrix: Linked requirements with corresponding test cases to ensure complete test coverage.
Example of a simple traceability matrix:
Requirement ID Requirement Description Test Case ID(s) Test Case Status(es) REQ-001 User authorization TC-001, TC-002 Passed, Failed REQ-002 Order creation TC-003, TC-004 Passed, In Progress -
Test Execution Reports: Contained information on the number of executed/passed/failed test cases, found defects, and test cycle status. Provided to the team and management.
The project used a Test Management System (e.g., Jira with Zephyr/Xray plugin or TestRail) for centralized storage and management of test cases and plans, as well as integration with a bug tracker (Jira) for defect reports. For automated testing, documentation also included results of automated test runs and framework reports (e.g., Allure Reports).