Moving forward to the next level in tools integration, with two-way synchronization.
Test management tools, of all types, have been recently busy adding support for bug trackers integration. Some concentrating on one specific tracker, others adding 2-4 trackers integration support.
At Testuff, we always thought it is the right approach. Test management solutions users, usually come with a set of already-in-use of other tools – automation testing tools, bug trackers, requirements management tools and more. It is therefore important to allow these users to continue working in their current environments when adding a test management solution, rather than forcing them to go and change other tools while implementing a new test management tool.
Taking into consideration that, in most organizations, the QA and development are still somewhat separated groups it is unlikely that the testing group will be able to force the development group to change, replace or add any tool of their set.
Knowing the relationship and the balance of power between these two groups, still in most places, this assumption holds ground.
Since our early days, back in 2007, we’ve been busy adding integration support for bug trackers. Starting with the most common and known ones (i.e. Jira, Bugzilla, FogBugz), moving to the second tier (i.e. Lighthouse, Mantis, Redmine), then simply adding new trackers integration by our customers requests.
We’ve been successful in integrating with trackers that are more of a challenge to integrate with (one to mention is TFS 2010), and to tools that are not bug trackers per-se (i.e. Clarizen, Basecamp) but which our customers report defects to even so.
With the years we have expanded and enhanced the integration, and while at the starting point we only allowed sending defects to the trackers, Testuff now supports many other options in the integration.
Covering one-way integration included a complete, full set of fields and parameters, to send all information to the tracker, for a full, transparent and comprehensive defect report. This includes video of the reported defect, the test details, control and customization of the defect report template, the tracker’s custom fields in the bug reporter, file attachment and more.
Two-way, fully synchronized integration
We’re now moving forward towards the next level of test management-bug tracker integration capabilities.
In the coming versions of Testuff, we will be adding full synchronization between Testuff and the tracker. This means that a Testuff user will be able to see in real-time the status of the defects as are in the tracker (and as set by the developers). It will also include an easy, fast way to get fields from the tracker and have them available in Testuff. This goes for defect status, and for Custom fields.
For the testing project manager or lead, it will be a great way to make sure the right tests are now tested and as soon as they can be tested (upon a defect closure, and a new fix release).
It will help improving the communications between the testers and developers, and speed things up for planning and managing the next cycles of testing.
We plan to continue and work to turn our strategy and philosophy about tools integrations into practice, step by step, version by version.