PractiTest Updates

5 cool features of PractiTest that hardly seen in any Test Management Tool

Last updated: August 05, 2010

Why PractiTest?

Sometimes potential customers ask us to help them understand whether PractiTest is the best solution for their needs. We believe that having Joel working with them to help define their process and customize the platform to their needs is invaluable.

But there are a number of additional cool features that make PractiTest a unique solution. We want to show you (only) five of them:

  1. Anti-Bug Duplication mechanism – Duplicates, bugs that are reported more than once in the system, are a pain for every organization. The overhead and the waste of time of looking for the original bug, defining it as a duplicate, and rejecting the new one is something that we all would like to save from our daily lives.
    What if you knew the bug you we are writing right now is a duplicate of an existing bug?
    PractiTest comes with a built-in solution to the duplicate-bugs problem: the minute anyone starts entering a bug the systems instantly displays the similar bugs candidates, enabling the user to decide whether this bug is a new one or not.
  2. Bug by mail – With PractiTest you can report Issues directly from your email client. This is great if you have customers or field engineers (sales, support, etc) who don’t have access to PractiTest, or if you want to forward someone’s bug directly from your inbox to the system:
  3. Unbelievable Customizations – not only can you customize the fields for your Requirements, Tests & Issues, but you can also implement your own user-permission levels and even define the workflow of your issues.
    Read more about PractiTest’s customization
  4. Hierarchical custom views – This is one feature that, once you understand how it works and the value you get from it, you cannot stop using it.
    The basic idea is that you can organize your tests-tree based on any fields you choose, for example release version, but ALSO, based on product component and sub-component, and ALSO based on Run Status, etc.
    Unlike folders where the Tests are only shown in one place, with views you can show a single test in multiple different trees based on your needs. This is similar to how gmail works with Tags, but BETTER!
    Read more about our hierarchal custom views.
  5. Integration with SVN – This is a must for many development teams who choose to work in this very organized way. For each issue you can see all the SVN commits linked to your issues, and also instruct SVN not to allow a commit without an issue being assigned to it.
    You can about our integration with SVN

Writing this post made me realize we have a lot more to write about, but maybe I’ll leave that to a latter post.

More flexible and scalable Test Management

Last updated: August 01, 2010

This week we performed a PractiTest system upgrade to implement a feature we’ve been planning for some time: a more flexible and scalable Test Management model.

This new model allows you to create and manage a Test Library with all the Tests you need to validate your application or system. It then provides a separate tab, called Test Sets & Runs, where you plan and run your testing tasks (or cycles) based on the tests already written and available in the Test Library.


This new model enhances the flexibility and scalability of your testing process:

  • Allowing you to create a test once in the Test Library and re-use it multiple times on your Test Sets (or even multiple times in the same Test Set).
  • Makes it easier to manage your test repository by having only one copy of each test.
  • Provides a quick and easy way to track the status of your test throughout their lifecycle by looking at all their runs from a new Test Sets tab available on each of your tests in the Test Library.


The new model is available by default in all PractiTest project created from this moment on.
Since we don’t want to disrupt the work in existing projects we will provide users with a period of time in order to migrate their projects from the previous to this new testing model. To migrate your project or to get more information simply contact your PractiTest representative or send an email to our support team.

PractiTest chosen by the Dutch Ministry of Foreign Affairs

Last updated: July 01, 2010

After reviewing a number of tools and alternatives, the Dutch Ministry of Foreign Affairs chose PractiTest for SaaS-based QA management for its outsourced IT projects.


“The fact that it was available to all parties involved simply through the Internet was one of the main reasons for choosing PractiTest. Another one was that there would always be a unified and up-to-date view of the project…”

“PractiTest helped us enormously to keep track of the project – progress and avoid misunderstandings”.

“With the help of PractiTest – customizations we were able to define new issue types and better cluster the information, allowing us to filter out data and generate more accurate and detailed reports. We recommended PractiTest within our Organization to be used in further projects”.

Read the full case study here.

PractiTest integration with JIRA, Bugzilla & FogBugz

Last updated: June 01, 2010

This week we performed a system upgrade with a feature that was being requested repeatedly by a number of users: the ability to integrate PractiTest with Bugzilla and FogBugz.

This upgrade also comes to improve our existing JIRA integration, and it enables Organizations to keep working with their available Bug Tracking systems, while allowing them to link these “external” defects into PractiTest and gain the traceability between the 2 platforms. You can learn more about this integration and how to configure it from our help pages.

In addition to the new and improved integrations (and to some additional issues fixes) this upgrade includes improvements to PractiTest’s import mechanism, helping users by providing more feedback on errors during the import process.

PractiTest Tour

Last updated: May 01, 2010

We just finished recording a new web-tour of PractiTest.

The Tour covers the Issues, Tests, Requirements and Reports Modules, as well as some of the platform’s customizations. We hope you’ll find it useful (click on the Play icon):

Feel free to send us your comments.

Mandatory system fields and additional Reports

Last updated: May 01, 2010

Yesterday we performed an upgrade that mostly included infrastructure changes and minor bug fixes, but also some of the features requested by our customers:

  • System fields can be defined as mandatory, just as regular custom fields
  • We included a couple of additional Reports covering Test Executions (the runs)
  • We added column sorting support for the Test grid
    Sort Support to Test Grid

Also for this upgrade there was no downtime

PractiTest on Facebook

Last updated: April 01, 2010

After many requests from the field we finally create a PractiTest page in facebook –

You are invited to become fans, check out what we are up to and receive updates from there as well.

Starting to support Exploratory Testing and adding a bunch of other good stuff in this upgrade

Last updated: April 01, 2010


We performed another PractiTest upgrade this weekend, and we’re happy to announce that we are starting to support Exploratory Testing sessions with the help of some cool new functionality:

  • You can create an empty test and start running it without steps, meaning that you can create your Exploratory Testing Charters based on a description of what you want to achieve with your test.
  • We added the ability to Add, Delete or Modify your Steps during the run of the test; so that as you progress through your Exploratory Session you can record the stuff you tested and keep the log for future reference.
  • At the end, you can update the original Test with the new / updated steps, so you can reference it or reuse it in the future.

In addition to the stuff above we also added features requested by users:

  • We modified and drastically enlarged our Custom Memo Fields.
  • After setting the run-step status to ‘Passed’ the focus on the page ‘jumps’ directly to the following step so that you don’t need to constantly scroll down.
  • We added the ability to see more than 20 lines in the Test and Issue grids, so that you can see more or all your data more comfortably:defined_number_of_rows2

And as always we included some minor fixes.

Let us know if you have any comments, issues or additional requests.

The PractiTest team.

MS Study finds that SMBs using hosted solutions perform better

Last updated: March 01, 2010

cloud_money-300x225We stumbled upon a report from Microsoft saying that Small & Medium Businesses using hosted services and solutions perform better financially than those using in-house software. You can check their press release here.

To summarize their findings, the study performed by a third party research firm showed that companies using SaaS and Cloud Based products, such as PractiTest :), showed higher revenues than those using traditional in-house solutions. The research also pointed at the fact that both awareness as well as the migration of SMBs towards SaaS solutions is growing year after year.

Michael Korbacher, a director in Microsoft, said that “Using pay-as-you-go cloud technologies, small and midsize businesses can now afford and easily have access to enterprise-class, secure services across any platform.

The study also quotes Dale Vile, research director of Freedom Dynamics saying that “This whole picture corroborates the notion that technology and hosted services can provide tangible business advantage, even for smaller companies, and it – not surprising to see that investment in IT and hosting goes hand in hand with good financial performance.

So what we always knew that makes perfect sense now gets a formal approval: SaaS solutions such as PractiTest are good for SMBs since they allow them to get the best possible products at accessible costs, and not only taking into account the price of the licenses but also the overall cost of installing and maintaining these solution in-house.