At last, we decided – PractiTest needs its own blog.
It wasn’t a no brainer, since we already have the QABlog that Joel posts almost weekly; so what’s the point in having another blog?
The main point is that in the QABlog, Joel mostly posts about QA Methodologies or his personal life & experience as a QA person; but PractiTest is growing fast and there’s much to tell!
So after struggling with the idea, we decided that the best way to go is to have two different blogs. Welcome!
- Views’ Tree in the Issues Module, – The popular Views’ tree in the Tests Module, is now also supported in the Issues module, allowing to create and work with hierarchical views in the Issues Module faster and easier. This came as a request from our customers.
- Ability to link between Issues and Test Runs (and vice-versa), giving an additional flexibility when tracking between issues and tests.
- And additional smaller features and fixes to improve your working experience.
Last week we participated in the IGT Cloud Summit that took place in Exodia, Tel Aviv. It was pretty fun and we’ve got some pictures to share. We also met some interesting companies who presented their ideas and product.
Our logo (part of the 20 ‘cloud’ companies that were presenting that day):
Joel also gave a short presentation, explaining about the real need for PractiTest that came from, yes, our users:
This weekend we updated PractiTest with some new and useful features, many of which originated from your comments on PractiTest’s Feedback Forum.
This upgrade comes with some exciting stuff such as:
- Jira Integration with a 2-way synchronization between PractiTest and Jira. (We will post a separate article with more information on this integration as well as the configuration instructions).
- In the Custom Fields settings you have the ability to Reuse the values of existing lists on new lists. For cases where you have one list that you want to use in multiple fields (e.g. Product Versions, Customers, Products, etc).
- Option to edit system fields (like Issue Type, Priority, etc). Modify their values, add default values, and decide whether to show them or hide them as part of your project.
- A new requirement traceability report, showing the end-to-end traceability from requirements, to tests, and to issues. You can access this report from the Requirements module, under the views and reports drop-down list.
- Global search in custom fields. Now each time you search for a word or phrase the system also searches in the custom fields you added to your project.
- Display of Step Number as part of the Test Editing and Execution windows.
- Ability to import requirements into PractiTest from csv files.
- PractiTest now remembers the status of the Requirements tree, so you don’t need to collapse it each time you re-enter the Requirements module.
- And additional small fixes.
As we already said, many of the features listed above came from your inputs, and so we invite you to continue telling us what’s you need so that we can continue developing the stuff that’s important to YOU.