How to present test case execution progress in Jira
Test Case Execution depicts a fundamental stage of the whole testing process. Speaking of, test execution follows the test plan preparation and relies on putting the complete list of test cases into effect. After gathering requirements, writing test cases, and putting a test plan together, during a test execution we can finally swing into action. As it constitutes the crucial part of a project, we can expect that the majority of stakeholders’ or customers’ questions will concern its effects. That’s why it’s so important to always be prepared and ready to present transparent data, understandable for everyone. RTM Test Case Executions report is presented as a pie chart with a table below it, so it makes analyzing the current status, testing progress and the results of particular test cases easier than ever.
Bring your tests into Jira with RTM
Both automated and manual testing consist of the succeeding steps. Executing those steps with one test management tool seems like the best way to go, as measuring the continuous progress can thereby be much faster and easier to achieve. When you have all your testing objects together organized with a dedicated app, like Requirements and Test Management for Jira, reporting from the particular stages is intuitive. First of all, you and your team members won’t have to collect the data from separate files or applications in order to make the report, because everything will be already gathered inside a tool during the earlier stages of testing. Many teams store their test steps and reports in external Excel sheets, but it often causes problems with unifying elements. If you decide on bringing your test management right into Jira and learn how to make the most of it, you will discover how many possibilities that solution can provide you with. In essence, if you already use Jira for your project management, your whole software development can be executed in a single place. RTM is fully integrated with the Atlassian suite, so it’s definitely worth a while to implement it in order to save much more time throughout the whole process.
Test and prepare reports in a single place
RTM not only makes it possible to store your testing elements, but it will also help with drawing conclusions. As it was mentioned before, our app includes the reporting features. For now, there are 3 reports that you can generate with Requirements and Test Management for Jira: the Traceability Matrix, the Requirement Coverage and finally the Test Case Execution, which we will describe in this article. All three of them can help you on a different phase of your product development, and we made sure they are equally useful and universal. The universality should be especially highlighted at this point, as other testing tools often have many reporting options. That doesn’t mean they have more possibilities, but on the contrary: it usually leads to the situation, when your team ends up putting multiple reports together, and spend a lot of time on it anyway. Reports in RTM allow to customize your data with filters, so you could get exactly the information you need right away.
Last but not least, the app provides its users with the Test Dashboard, where one can display all previously generated Test Execution and Test Case Execution reports. Seeing all the reports on a single screen makes it much easier to track the progress and speeds up the communication of our test results to other stakeholders. The dashboard is practically ready to show on meetings, so it saves up a lot of time and energy which otherwise would be spent on creating diagrams separately.
Test Case Execution report
Setting up your data
The TCE report presents the statuses and progress of Test Case Executions for particular Project, Test Plan, Execution, RTM Environment, TCE Created Date and TCE Assignee. Before generating the report, it’s best to analyze what exactly we would like to display on the dashboard in order to avoid unnecessary information that could distract our attention. First, we need to choose the project and the specific test plan. After that, in the Execution field we select the ordinal number of required test plan execution. RTM Environment defines in which system our tests were performed.
Test Case Execution report shows the statuses of the particular test cases according to the choosen filters
Generated report has the form of a described pie chart. Above the graph we can see the number and the percentage of passed or failed test cases. We can also track what part of all tests are passed with restrictions, in progress, blocked by other ones or yet to do. Below, there is a table with summary and details of each test case, such as its priority or related defects. The dashboard can be exported to a .pdf or .csv file ready to present to the stakeholders during a meeting.
A transparent pie graph and a table below illustrate the testing progress
How to make the most of TCE report?
Software systems get more and more complex, so their testing process must be managed with great caution. The more advanced the product is, the more objects must be tested before the final release. RTM Test Case Execution report is fully flexible and prevents getting lost in the great number of test cases and their statuses. By clicking on the Preferences icon in the upper right corner of a table, we can select which type of test case execution status we need the dashboard to show. It’s best to use it when for example we’d like to see only those test cases which turned out to be failed in order to fix them. As each status has a different color, a pie chart clearly illustrates which part of the process is already completed, so it will be easier to estimate the amount of time that the team members need to finish their work. As it’s possible to filter executed test cases by Assignee, TCE report allows to check who is responsible for each task and coordinate the workflow. Sorting cases by RTM Environment lets us spot in which system the product may be the most problematic to use. TCE Create Date turns out to be very helpful when it comes to productivity tracking in Agile model: the product manager and other people responsible for the project can verify the progress of all test executions planned for the specific sprint.
Know your testing progress at a glance
Testing inside Jira has a lot of advantages that your team will feel immediately after implementing this solution into your software development. Above all we can distinguish three of them:
- it speeds up the whole process by eliminating the necessity of using external tools;
- all the objects gathered in a single place make testing more efficient;
- transparent, well-known interface lets everyone track every step on the way.
Test results reports available in RTM help to achieve it all. After you choose the required data, Test Case Execution report will allow to verify the progress of test cases contained in each test plan, during all performed executions. Both the pie chart and the table show statuses of test cases and make it easy to check which part of the work is finished and what’s yet to be done. This also makes it possible to estimate the time remaining to complete the process and organize your teams’ workflow the smartest way possible.
If you’d like to test Requirements and Test Management for Jira (RTM) yourself, take a free 30-day trial from the Atlassian Marketplace. You can also book a live demo via Calendly, if you’d like to see the app in action, or read more on bringing test management process inside Jira on our blog: