Below are the phases of Sofware Testing Life Cycle suggested if you are working with Magellan
- Requirement Analysis
- Test Planning
- Test case development
- Test Environment setup
- Test Execution
- Test Result Reporting
The table below provides the role of Magellan as applicable to each of the different phases of the testing life cycle. Below steps is a general recommendation and local test practices might override the steps below.
| STLC Phase | Test Context | Magellan Context |
|---|---|---|
| Requirement Analysis | Test team studies the requirements from a testing point of view to identify the testable requirements. The test team may interact with various stakeholders (Business Analyst, Technical Leads, System Architects etc) to understand the requirements in detail. | Test Team as per analysis of the requirements decides the tests and then as part of further analysis decides which tests to automate. |
| Test Planning | Tester identifies and writes the test scenarios. Detailed test steps not written at this stage. | Step 1. Create Test Suites Step 2. Create feature file Step 3. Create scenarios REQ-REF in the test scenarios allows requirements to be tracked back to requirements allowing creation of a requirements traceability matrix (RTM). Step 4. Commit to GIT. Magellan provides the capability in the tool to commit to GIT without usage of any other source control tools. Use source control tools if you are using source control systems other than GIT. (Magellan does not have the ability to push to remote – separate GIT client is required) Note: In certain cases rather than create modification of existing scenarios will be needed. Make the necessary changes and commit to GIT (Step 3). |
| Test Case Development | Write detailed test steps. If test data requirements are known add to the test scenario. | Step 1. Write detailed test steps You can write data driven scenarios as well Step 2. Commit to GIT Note: As test steps are written often there might be issues observed. More info about troubleshooting failures during test scripting at Scripting. |
| Test Environment Setup | Deliverable of this phase is a test environment ready with test data set up. | Magellan as one of its primary benefits allows testers to spin up local environments at a branch level and provide early feedback to the configuration developers. |
| Test Execution | Execute tests as per plan and document test results. Log defects for failed cases. | Automated Tests Step 1. Execute testsTests could be executed locally Step 2. Watching tests run Step 3.More info about troubleshooting failures during test scripting at Execution Step 4. As tests fail defects shall be logged in the defect management system Manual Tests Step 1. Execute Tests Step 2. Record test results |
| Test Result Reporting | Report showing the quality of the tested product which allows making a decision on the software release. | Search test results For tests passing search using CTRL-SHIFT-F and enter @manual-result: PASS For tests failing search using CTRL-SHIFT-F and enter @manual-result: FAIL Note: Magellan does not have an inbuilt test execution history database. If you have an inhouse test management system talk to Foster Moore about linking Magellan to test management system. Additional capabilities to be built into Magellan and can translate to additional project costs. |
| Defect Retesting | Testing performed to check the test cases that were unsuccessful in previous runs successfully pass after the defects are repaired. | Step 1. Search for the failed test cases using defect tag search using CTRL-SHIFT-F and enter @<defect tag>: <defect number> Step 2. Execute failed tests For automated tests:please follow failed tests on automation Step 3. For manual tests update results |
| Regression Testing | Testing executed to check whether a code change has not unfavourably disturbed current features & functions | Step 1. Search for subset of tests Step 2. Execute tests For automated tests execution For manual tests: Execute tests and update results Step 3. Update results Regression tests could also be run via Jenkins. |
| Test Closure | A check against the test exit criteria is very essential to claim that the testing is now complete. Before putting an end to the test process, the product quality is measured against the test completion criteria. | Test results in Magellan could be used against the test completion criteria. |
0
