Headstart Learning Management is a software system that has gone through almost six complete versions with different customization both feature and interface wise as well. The testing of the latest version was properly planned and processed methodically with the use of a Software tool to create the test cases and report issues that mapped as their results.
JIRA test cycle set up
JIRA is the software that we are using in our company for reporting bugs, add tasks, improvements, Epics and suggests to add new features to the different types of projects. JIRA is great for manual testing, reporting and tracking. Before we integrate JIRA with zephyr our software engineers access the bugs, task, and improvements and fix them that are assigned from JIRA and fix them according to their priority level. But now Zephyr for JIRA enable our developers, testers and our entire project team to be better prepared at every stage of the software lifecycle and plan, build, test, execute and launch a great software. The main reason to integrate JIRA with zephyr is that Zephyr Enterprise Edition is a real time Test Management system which can efficiently integrate with JIRA. So I could add issues into as test cycles into our integrated new system with Zephyr.
In the upcoming descriptions I have explained how our testing process was layed out from the scratch, and we aim to use the same test cycles to execute at many versions that is to come in future.
Creating test cases
I am creating a test case just like any other issue type in JIRA but the test has additional fields and capabilities. Test Cycles page can be accessed on the left or from the “Plan Test Cycles” menu item in the top level “Tests” menu. The “Ad hoc” cycle is default in every version and if there is no version available for the project then it is listed as “Unscheduled”. I create test tests and configure the fields according to our test requirement. I will add the ID of the tests and then get added to the Test Cycle.
Add test cases to cycles
Once a test has been created the next logical thing to do is execute it. Executing a test means providing a high level status on what happened. The progress tracking status bar provides us a quick view on how many tests have been executed and what percentage of the overall testing has been completed for a test cycle and different status colors. Once a test has been added to a cycle either for future execution or as part of the execution it is displayed under the cycle. It can be executed from there by clicking on the “E” button (Execute test).
Execution and issue reporting
I add test details section for every test cycle. This allows to enter detailed test steps, accompanying test data and expected results. Test steps can be reordered or deleted. Also if the execution status fails I add the relevant defect number mentioning the issue which is not yet solved and a comment why it failed.
Test summary and retesting
Test summary page explain how many test cases are left to run, how many test cases you have per iteration or component. So this view provides summarized information about the test repository. We can reuse test cycles for other versions of the same projects and new other projects also. When the software engineers fix the issues I’m verifying them and close them. Using the Zephyr plug in for JIRA for our projects is a great way for QA and developers to manage and monitor tests and execution status in real time.
The best part of having this process laid out is that, it make the testing process more efficient and standardize the steps to follow. We believe this process will be very effective on our goal of producing a bug free systems in future developments done at our Innovation labs.