Updates

PractiTest Maintenance Notification – Saturday, August 9th, 2014

/ August 5th, 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

Better Test Sets & Runs Navigation

/ November 28th, 2013
 

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

New Test Legend

New 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.

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?

/ October 31st, 2013
 

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

/ October 28th, 2013
 

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 Preview

Issue Preview

Test Preview

Test Preview

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.

Work better now with PractiTest new & improved GUI

/ September 17th, 2013
 

Ever since PractiTest was launched, we have always made sure to be in tune to our users’ adaptive needs. Taking into account your requests and feedback we have implemented some changes, refreshed and improved our GUI.

Now we can proudly announce our GUI update – “PractiTest Style 2013″. The new style improves and streamline your daily processes, so now you can work in a more organized and intuitive manner.

 

Here’s a glimpse of the improvements:

 

New PT GUI

Neutral colors and smart design

One of the first changes you’ll notice is the new color palette. Neutral colors that will help avoid distractions so you and your team can concentrate on your work.

 

 

 

 

Edit Screen

“New” and “Edit” screens

You will notice the new “Edit” and “New” screens have a new design, with easy input fields and better use of the space on your screen.

 

 

 

step_run

Tabular step run window

A new and more useful design for steps in Test Sets & Runs, This new design integrates all the functionality of the extended view with the advantages of the compact view.

 

 

 

 

rolloverRollover  Preview 

The “old” GUI used to have a right pane in the various modules, which made the whole grid look awkward. So we took it away, and added a popover when hovering those items, to see the fields. The popover was added to most of the entities in the program.

 

 

Better support for tablets!

As it is now common use to work on tablets while testing operations, we made sure the new GUI was able to re-size itself and adopt to the various platforms you might use.

And there is so much more!

If you want to get some more technical information about the new GUI, we refer you to our previous post: PT GUI change – what and how

___________________________________________________________

We know that sometimes changes can prompt questions and so we will be more than happy to assist you any way we can via our support team.  We will also be delighted if you want to write to us to share your thoughts and comments on this new GUI.

We hope that you like what you see.  And thanks for using PractiTest.

- The PractiTest team

 

 

 

Comments are closed.