PractiTest Updates

Here are some of the November 2018 updates to the system:

• JIRA Cloud integration improvements : A modal box that appears after pressing Fail & Issue within a test run. Thus the issue description can include all the steps’ information without any limitation. And the ability to report issues of type sub-task into JIRA from PractiTest. (JIRA Server improvements are on the way and will be released soon! ) More about this in our discussion forum

• We take your privacy and data security very seriously. That is why we have invested our efforts to comply with leading data security standards. We are now fully compliant with:
  
  • ISO/IEC 27000
  • SOC 2 Type II
  • GDPR
• We are glad to announce that we will be opening a new data center in the EU. If you are interested in switching over please contact our support.

Hi,

As we are constantly updating PractiTest with new functionality and small fixes, we’ve decided to send monthly updates describing the major changes and improvements.

Here are some of the recent updates to the system, done in month of October 2018:

• Exploratory Testing module improvements. Based on your feedback, we are updating the ET functionality so that you can get the full traceability and re-usability of your Exploratory Tests too. With this update, Exploratory Tests are now part of the Test Library, and can be added to Test Sets like any other Test.
  * This improvement to our Exploratory Testing feature was released on Nov 3rd, but it’s a large change, so we decided to add it to this update.
• Multi-Factor Authentication (MFA). A new optional extra security layer for users to log-in, while being protected from brute force and social engineering attacks.
• Create test cases from Test Sets. Another request from multiple users, in order to save time by working directly from the Test Sets and Runs module.
• Autocomplete feature within ‘List’ custom fields, including the ‘Version’ system field, as requested numerous times in our Uservoice.
• Select fields from different entities when creating Instance Dashboard graphs
• We’re now SOC2-type II compliant, Learn more about the security measures we take to ensure your data’s safety.

And of course, there were other bug fixes.

– Prioritize your tests

– Add a comments field to your runs where testers add comments when they run the test

– Once a quarter sit with your Business Stakeholder and review your tests

–

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.

Free Trial

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.

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.

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.

Learn more

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

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.

Read more about Test Sets and Run