Moving to markdown

Last updated: Jul 02, 2017: 11:19AM

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.

markdown for steps

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)

Last updated: Jul 05, 2017: 7:32AM

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 test annotations new exploratory test

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

Updated application navigation bar for increased usability (and Step Parameters)

Last updated: Nov 09, 2016: 9:52AM

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 –

navigation bar update

 

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) –

disabled menu options

One last time saving GUI change is we have moved all project settings to an quick access drop-down menu –

project settings 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

Last updated: Jul 07, 2016: 11:14AM

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.

 

step run update

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

End to end Integration with JIRA

Last updated: Mar 22, 2016: 2:22PM

Yesterday (Saturday 23rd) we upgraded our integration with JIRA Server, JIRA Cloud

End to end traceability of your Jira Requirements and Issues in PractiTest

JIRA with trade mark

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.

JIRA_Integration

 

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.

 

JIRA_SERVER_settings

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 help page.

PractiTest Maintenance Notification – Saturday, August 9th, 2014

Last updated: Dec 22, 2015: 10:53AM

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

Better Test Sets & Runs Navigation

Last updated: Mar 23, 2016: 11:45AM

Hello to all PractiTesters!

Recently we performed another update of PractiTest with important additions to make your work better and more effective. Let’s start with some additions to make your work clearer, specially when you are only getting started with the system. We believe that each tester (or non-tester) working with PT should understand our methodology (and read the page at least once).

As part of our Testing Methodology you can see that:

  • A Test Set is a collection of Test Instances
  • An Instance is linked to a Test (in the Test Library), so that each Test can be linked to multiple Instances
  • Each Instance can have multiple Test Runs (where the status of the Instance is the status of its last Test Run).

The Test Legend

To avoid confusion (“where am I right now?”), we added a Test Legend in all testing related entities, indicating the location in the application. We believe that especially for new PractiTesters, this legend will help understand our methodology and the links between the different entities.

test_legend_instance

The standard Testing Scenario

  • Each Test (in the Test Library) is defined only once, with all its relevant steps
  • Test Set creation, and their respective Instances, are defined once in a while when there’s a reason to start running these tests ( e.g. a new version /release, new functionality, etc).
  • Whenever a user goes to the Instance, and presses the Run button, a new Test Run is created, copying all the steps to the test run (so if the Test in the Library is changed later, the steps in the run will not change)
  • If for any reason, an Instance needs to be re-run in a specific Test Set, the tester will create an additional Run and not overwrite the previous run.  Ensuring all run history is saved.

Better Test Sets and Runs navigation

In addition to the above we decided to streamline the testing process, making the run button much more powerful, and skipping some screens when they’re not required:

  • If the user starts a Run from the instance grid, and the Instance has no required fields or older runs, then it goes straight to the run window (with the steps). Enabling to start and testing right a way.
  • In cases when there are required fields in the instance that are not filled, it will go to the instance window.
  • And in the case there are older runs (that you want to review before starting your new Run!), it will go to the instance window, showing previous runs, enabling to go and check or update one of those test runs.

We are sure these changes will make your testing experience more productive.  And we invite you to share with us additional ideas to make your work even more effective in the future.

An interesting take on current events: What Can IT Project Leaders Learn from the Healthcare.gov Fiasco?

Last updated: Oct 31, 2013: 12:14PM

The latest news headlines regarding the healthcare.gov debacle are an excellent example of how not to launch a new website, application or any other IT product. The common development pitfalls — lack of visibility and communication were imminent throughout the whole development process.

As many of you will agree, lack of visibility and communication are illnesses suffered by many software development and IT projects. The problematic signs are usually there, but they are not communicated to higher management.

Without the proper visibility into the process and without the ability to understand the status of the project at all times, management cannot make the correct decisions to ensure the success of the project. Healthcare.gov is an unfortunate example of the catastrophic consequences of noise interfering with the message communicated to higher management.

How can such problems  be avoided? …   More on the subject in our latest PR release 

Improved Preview popovers – only by a button click

Last updated: Dec 21, 2015: 10:53AM

Since we released the new GUI last month, we got some amazing feedback from our users.

We did an online survey, to explore more about the things you liked and those you though we could still improve and we found that although most of you really loved the changes we did, you still thought we had some things that could be improved.

Issue_popover

Test_popover

Many users found it annoying that when they moved their mouse over the id in the grid, the popovers would open automatically; and we also had couple of bugs in this feature (which we fixed in one of those patches we’re doing all the time…)  We even added a place in the personal settings to disable those popover from popping automatically.

But we really think this is a great feature and so we decided to solve the issues that were “annoying” some users.  We started by changing the functionality so that when the mouse is over the id (hover), we now show the “info” button, enabling the users to click to see the preview but only with a mouse click;  and another mouse click to close it.

In addition, we added some useful information to those previews. Tests -> now you can see the first 5 steps, TestSets -> now you can see the first 5 instances, Requirements – > the traceability.

We are sure this feature is now a lot better and it provides even more value than before.

Note: the disable popover flag in the personal settings settings works (turns off the popover) in the places where the feature would have been opened in the “old way” without pressing on the popover button (not in the grids).  But we foresee that in the next couple of releases this flag will become irrelevant as we migrate all the popover functionality to work as it is doing in the grids today.

Choose the best way of working now!

PractiTest – all rights reserved / The website was designed & developed by Chilid

SaaS Test Management Tool and QA Management Tools - PractiTest