We know of a number of reasons people like using PractiTest.
For example the idea of running tests and reporting issues automatically when a step fails, without needing to manually add all the steps to reproduce the bug.
The fact that all the testware (Requirements, Tests & Issues) is located in the same system.
The easy of use and simplicity of the User Interface.
And these are only a few…

Still we also see companies who are interested in using PractiTest as their Test Management Tool, but don’t want (or can’t)  move their whole R&D team to work with PractiTest as their single Issue tracking system.  After receiving a number of requests from companies like these, that are also using Jira, we developed an Integration between Jira and PractiTest.

One of the main difference in our approach is that, unlike many of the other tools integrating with Jira with a 1-side only integration (where bugs submitted in their tool are only copied to Jira and then the link is cut), we implemented a 2-way synchronization that allows our users to still take advantage of our Bug Management as well as our Test Management functionality:

• If you create an Issue on PractiTest you will see it on Jira
• If you create an Issue on Jira you will see it on PractiTest
• When you edit or update an issue, either on Jira or on PractiTest, you will see the changes on the other tool
• So if there’s a bug that originated from a test in PractiTest, you will see all the steps also in Jira, and you will be able to go to the Test in PractiTest directly from the Jira window.

The integrations requires some configuration and mapping (for the fields and their values in both tools) before it starts, but this configuration makes it very flexible and a lot more intelligent than simply copying the default system fields as they are.

The bottom line is that it took us more time than we originally thought it would take to develop this integration, but we think we are on to something good.  So I’d like to thank all the users who keep working with us on this project and giving us feedback on the plugin, and to our R&D guys for developing it around the clock.

PractiTest-Jira Integration Help

Greetings!!

This weekend (November 6th) we performed an additional update to PractiTest incorporating some useful and important features into the system.

Some of the most important additions are:

• Batch edit in Tests – where users can either select individual tests or whole views and perform batch modifications to the fields in the entities.  (We are experimenting with this editing mechanism in the Tests module before deciding whether to implement it in the Issues module too, feel free to tell us what you think).
• Navigation Mechanism in Issues and Tests – allowing users to navigate from entity to entity in their views without needing to go back to the grid.  A small improvement that we think will save a lot of “clicks” to our users.
  

  PractiTest navigation controls

• Enhancements to the test cloning mechanism – allowing users to choose tests one by one before cloning a new Test Suit.
• Improvements to the folder management mechanism in Tests - allowing to edit and move folders more easily.  Starting from this update, you can also clone tests from folders too.
• Additions to the Jira integration plug-in – based on the initial feedback we received from our users.
• And many smaller features and fixes throughout the system.

Many of the features above came from the feedback provided by our users in PractiTest’s Feedback Forum.  We encourage you all to keep telling us what you want and need, and we will do our best to fill out your wishes…