PractiTest Updates
5 game changing features by PractiTest
Looking at different test management tools and comparing them is boring. Yes. I said it. They all say the same and seem to be doing the same. Well, we in PractiTest are working hard to give our clients far beyond the features and solutions they can get anywhere else. We design our product by looking into our clients job, talking to them and listening to their pain points. We gathered a few of our best features for you. These are features you can’t find all together anywhere else, definitely not on the same quality level as can be found on PractiTest . They will help you organize your process, and will give you back great benefits that translate into time and money saving!
Enjoy!
- No more data mining! Hierarchical filter trees + Advanced search – PractiTest offers you a whole new way to look at your data. Having hierarchical filters means you can slice and dice your data to your convenience. It’s a simple setting that organizes your data in a dynamic way instead of leaving it static. Its like tags but much smarter. Add our faceted search to that and your you will never look at your data the same way. Check out this video to better understand
- Fully customizable and adaptive – With PractiTest dynamic structure you can start using the tool “as is” and easily customize it to your (often changing) needs as you go. You can customize your fields (enabling custom views), implement your own user-permission levels, define the workflow of your issues, and reuse your existing data in a smart quick way. Even our pricing is scalable. So no matter if its your team that’s changing, your organization or the whole market – we’ve got you covered.
- Never work twice. For real. We can do it.
– Permutations – YES, permutations. No more clone change clone change clone change… tell us the basic variables you want to check and we will do all the mix and match for you.
– Step parameters + call to test – write a test once, use it multiple times in different ways and customise it easily each time. learn all about it here
– No more duplicated bugs. A unique solution you can read about here
- Communicate with PractiTest in more than one way –
– bug by mail – external team members are able to report bugs by mail. Amazing.
– External dashboard sharing and advanced reports – Your boss will see the real deal now. In a way that will blow his mind.
- Advanced integrations – more than just transferring results. Our system can actually TALK to other systems.
We have some more cool unique features. The best way to learn about them is by setting a free personal demo here and discuss how PractiTest can answer YOUR specific needs.
N/A status is going all the way to Runs, Tests, and even Requirements
For better transparency of your testing efforts
Remember this?
It’s the N/A step status we added last year as we saw the need for Not Applicable status.
We took this further and from now on, in case you mark all the tests in a test set/run as N/A, the Run status will change to N/A accordingly
(the same applies also to the Test Status, or even the requirement status)
This small GUI change gives an even more accurate and clearer view into your testing status, enabling you to communicate “neutral” testing efforts as they are, and not appear as “no run” like previously.
From today (Nov 29, 2017) at 7:00 AM UTC, N/A statuses will be calculated and updated all the way from the steps to the requirements. Previous runs with N/A steps, are not touched (and considered as NO RUN), mainly since we didn’t want to touch the history of your runs.
Moving to markdown
In the last couple of weeks, we’ve been working hard to shift our previous description fields which were HTML based to markdown. The reasons to shift are many – it’s easy, fast, clean and more.
It also enabled us to upgrade the editor we had to a simpler markdown editor, with better UI capabilities and fewer bugs. We were also able to enable rich editing in the steps’ descriptions and expected results, that was not part of the application before.
And in addition to all that, if you now export and import tests from and to PractiTest, the style remains, which makes it even easier to migrate data.
Anyways, to cut the story short, we’re markdown! Enjoy the rich editing in steps attributes, and the (almost) bugs free editor.
Take into account that old description fields (of tests, issues, requirements) were all migrated to markdown (from html). Let us know if you find any issues.
Session Based Testing (Exploratory Testing)
PractiTest now includes a new type of test that supports Exploratory and Session Based Testing practices.
- Quick and intuitive – Create Exploratory tests as test instances “on the go”
- Run Exploratory Testing Sessions and create annotations for easy tracking and collaboration
- Report Issues from run – works with all your existing project’s integrations
Exploratory tests in PT allow you to define Charters for your ET Sessions, document annotations as you are running your tests, report bugs directly from your runs, and finally to review your ET sessions with colleagues in order to gather feedback.
Unlike other tests, which are created first in the Test Library and then added to any Test Set (new or existing) before running, the Exploratory Test is created as an instance in the TestSet and Runs module “on the go”, which is more intuitive and supportive for exploratory testing methodology.
Now your Test Sets can contain all types of tests at once: automated, manual and exploratory. This ability to combine various tests improve QA coverage and trace-ability.
Updated application navigation bar for increased usability (and Step Parameters)
PractiTest’s latest navigation bar update separates Project related setting and actions, such as: search, requirements, tests, reports, project settings; from other General application actions such as: user settings, help, tutorials.
This modification makes navigation more intuitive –
You will also notice that all menu options are presented and are actionable based on permissions, un-permitted menu items are disabled and colored grey (used to be hidden) –
One last time saving GUI change is we have moved all project settings to an quick access drop-down menu –
New Step Parameters [Enterprise only]
This week we also relased Steps Parameters: a cool way to increase Test reusability – Learn more
New Step status: N/A
A small addition to your steps run that will make a big difference:
- Now you can choose to set test step status as N/A (Non Applicable) and reflect an accurate testing status.
- Test status will be based on all other steps in the Test run and can be marked as completed.
This small GUI and functionality change is helpful, because it means you can now define certain steps “neutral” so they don’t affect the final run status, and you can still pass tests with N/A steps, rather than the previous “no run” option.
This is meant to give your team and project members a more accurate view of project status.
End to end Integration with JIRA
Yesterday (Saturday 23rd) we upgraded our integration with JIRA Server, JIRA Cloud
End to end traceability of your Jira Requirements and Issues in PractiTest
See JIRA issues directly in PractiTest
JIRA users can now see their JIRA Issues directly in PractiTest including all the relevant testing information.
Linked issues are synced to PractiTest in real time.
Integrate Requirements into PractiTest
Your requirements/User stories are now a part of your testing.
Users can now link requirements directly from JIRA to PractiTest and have testing traceability from end to end, including:
Requirements, tests, issues and the relevant reports.
Requirements are synced from JIRA to have information at PractiTest updated at all times.
Users can choose to link/unlink the Requirement from PT to JIRA.
New projects are now easier to set up than ever before.
Project, issue and PT IDs are automatically populated from your JIRA projects.
Start working with this integration today
JIRA Cloud users : Update was done automatically!
JIRA Server users: Please update your PractiTest-JIRA add-on and contact us.
For more information, please review our JIRA integration page.
PractiTest Maintenance Notification – Saturday, August 9th, 2014
Hello,
As part of on-going operations to improve the functionality and the performance of PractiTest we will be carrying out maintenance operations to our servers during the weekend of August 9th, 2014. Even though most of our maintenance does not usually cause any downtime, this specific operation will require us to have some downtime in our service.
In order to minimize the impact of this operation we have scheduled our maintenance to happen on Saturday, August 9th, 2014 at the following time:
- GMT – 5:00 to 9:00
- CEST – 7:00 to 11:00
- Eastern US – 1:00 to 5:00
- Pacific US – 22:00 (Friday Aug 8) to 2:00 AM
- Eastern Australia – 15:00 to 19:00
You can follow our live updates for this operation via PractiTest’s Twitter account.
As always, we will be more than happy to provide additional information and answer any questions you may have. Feel free to send your questions to our support.
Best regards,
The PractiTest Team
Can PractiTest support Agile Test Management?
Agile Development and Agile Testing
Today, more and more teams are shifting over to AGILE. One of the interesting facts about agile development is that it comes in many variations, from Scrum to Extreme Programming and more; but regardless of the approach you follow there a number of principles in agile development that everyone agrees to:
- Customer satisfaction is achieved by frequent delivery of useful software
- Changes in requirements are part of the software development process
- Regular adaptation is needed to comply with the changing circumstances
When you work based on frequent deliveries, constant changes and regular adaptations; how can you still manage an efficient testing process?
Part of the philosophy behind agile development & agile testing talks about shifting towards automated testing as the means for covering regression testing & test driven development to achieve more stable code from the beginning. This “advise” is helpful but it still falls short from providing the solution and the guidance needed by a QA team to cope with the challenges of shifting to AGILE.
There are books that talk about this, and Joel wrote about agile testing in his blog. But in the end there is nothing like the experience from working with many organizations that shifted to AGILE with the help of PractiTest, and from the knowledge we’ve gain from our own experience developing PractiTest as an agile team. The tools you use will help you achieve your testing and development goals in the same way that a hammer and the nails help the carpenter to make his furniture, and flexibility & adaptability is a must when you are looking for a tool to help you manage your agile process.
PractiTest Test Management Solution for Agile Development
A quick search on the Internet will show there are many solutions specifically designed to handle agile development, and some of them even claim to support agile testing, but we still see many customers who check them out and find they are missing important functionality needed to cover the testing process.
As a methodological test-management solution, from time to time we are asked to show how we support agile development and testing, and an interesting fact is that we support Agile Testing without having any specific feature developed solely for this purpose!
How do we do it? The answer is simple, we believe in flexibility. PractiTest enables YOU, the user, to customize the system based on your process, your product and your needs.
If you working based on sprints, for example, you can customize the system by creating a custom field called SPRINT and adding it to your requirements (or user stories), to your tests and to the issues in your project. Once you have this field in place you can organize all your data and work based on the sprints you defined. You can then create views and reports that will make it easy for everyone to gain visibility into their tasks and those of the team and allow the whole team to manager their work fast and easily.
What’s even best is that you can modify the values in the fields and even the fields themselves with a small number of “clicks” and in a matter of seconds (without the need to of complicated customizations or processes).
Another aspect common to Agile Testing is the popularity of Exploratory Testing among testers. This approach works mainly by defining testing charters up front and documenting your testing steps at the same time you execute the tests. In PractiTest this is easily achieved with the functionality available that lets you edit your tests steps even when you are running them within the Test Sets & Runs module.
There are many aspects that define Agile Development & Agile Testing, and the truth is that each organization and even each team will approach Agile in their own individual and different way (based on their needs and their constraints). In this same way, we believe that it is not correct or even possible to try to define for you how you should manage your agile testing process. The best approach, the one we believe in, is to give you the freedom to let you decide how to work and to support you process your way!
More information about custom views and custom fields.