This is a blog article which intents to review PractiTest, one of the best test management tools available in the market. It helps you ease the testing and development process. Sharing quick feedback to the team after QA activities is important to deliver high-quality software to the end-users. Sharing the test results in an excel sheet as an attachment has become obsolete. Your managers have to view/analyse the test results quickly in order to take decision. Let's say you present the test results in a web dashboard, then it makes it easy for the entire team to understand the outcome of your report post successful completion of the testing activity. Let's see how you can manage test cases and share the test results in PractiTest.
PractiTest is an application life cycle management platform. You can manage the requirements, test plans, test cases, and issues effectively. It helps to share the test results to everyone. If your team has already started developing the application without a test management tool or is fed up with the current tool, you can easily import the existing artifacts in PractiTest and start managing the tests effectively.
You can link the defined requirements with the test cases to achieve traceability. PractiTest provides end-to-end visibility. When you perform test execution, it will reflect the status in Test Library and Requirements modules in PractiTest.
Test case Management
Using a complicated test case management tool always increases maintenance effort. The tool should be simple enough to manage and define test cases. The idea of PractiTest is to divide test cases that are created, imported to and stored in the Test Library, from the Test Sets & Runs where you group those tests according to relevancy (for example - cycle, sprint etc) and run them as instances. Unlike other systems that work with static folders, PractiTest uses dynamic filter trees (based on system and custom fields) to organize all testing data. With filter trees, a user can slice and dice his data according to what he needs and create customized dashboards and reports to other stakeholders based on the data relevant to them.
Jira is a most widely used Project management tool. Test management tool without Jira integration neither adds any value to your team nor your project. In PractiTest, you can import requirements from Jira by just providing Jira Ticket number. When you make any changes to a Jira ticket, the changes will be reflected in ParctiTest immediately. You can also create Jira Bug ticket when executing your test cases. Linking between the test case and the Jira Issue will be established automatically when you create a Jira Bug from PractiTest. PractiTest provides JIRA Two-Way Integration feature. i.e. you can view test execution status in Jira ticket for the linked test cases.
You can set execution time for each test case. This feature is helpful to determine the difference between actual and expected test execution time. When you induct new QA engineers in your team, time duration details will make them to understand how much time need to be spent for individual test case.
Automation Testing with PractiTest
One of the main ideas of PractiTest is to enable visibility to the entire testing process including automation. The system integrates with automation using REST API and Fire Cracker. You can update test case status by calling PractiTest API from your automation testing framework. Since this is an API call, you can integrate PractiTest in any test automation codebase. The following test case statuses - PASSED, FAILED, BLOCKED, OT COMPLETED, NO RUN can be sent from automated test script.
Firecracker allows you to take XML report files from any CI/CD tool and upload them into PractiTest. From now on, every time you have new build results, they will be sent to PractiTest where you will be able to see the results of your entire software development and deployment processes in one solution.
PractiTest integrations include the following systems: Jira Cloud, Jira Server & Datacenter, Pivotal Tracker, Bugzilla, Youtrack, Azure DevOps, CA Agile Central (Rally), FogBugz, GitHub, GitLab, Trac, Mantis, Assembla, Lighthouse, Redmine , Slack, SVN, Zapier, AND Jenkins.
PractiTest has Exploratory Testing module which allows you to define test charters & guide points for your exploratory sessions and save those guidelines as test cases for future reusability. When running the ET test case, you can document important points that arises in the annotation section as well as report new issues or links existing issues.
If your team is not using Jira for Agile Development Process, then you can very well use PractiTest to save the artifacts. For example - You can use Requirements module to define User Stories & Test Library module to create Acceptance Tests. You can use the Dashboard to keep your team up to date with the status of the Sprint in General and of each User Storie in particular.
Without a proper testing report, your team cannot take appropriate decision during a release. Spending time to prepare test reports is a waste of time. Quicker and quality feedback help your team. PractiTest provides pre-defined report templates (Tabular Report, Tabular Aggregated Report, and Detailed Report.) You can also modify report columns & graphs based on your needs and schedule the reports to send on daily, weekly or monthly basis.
Test Steps Resusabilty
Let's say your testers are writing test cases for two functionalities which are almost identical, then you need to reuse the test steps instead of duplicating them. PractiTest allows you to call test steps from another test to enable reusability.
As a leading software testing company, we have used a wide range of software testing tools for our QA projects. If you are planning to evaluate test management tools, then don't forget to add PractiTest in your list. It comes in three basic versions namely Professional, Enterprise, and Unlimited. You can signup for 15 days Trial period for thorough evaluation. Please note - for automation testing integration, we recommend Enterprise plan.
We hope you've enjoyed reading this blog article as much as we've enjoyed writing it. Contact Us for your QA needs.
A fool with a tool is still a fool.