“With PractiTest we manage testing of three separate applications (ERP, point-of-sale, and payment processing). This means that separate QA teams in different sites use PractiTest to manage tests and bugs.
No doubt, this is the best product in its price category: PractiTest is solid enough to support multiple testing environments and complex scenarios, yet it’s very intuitive for everyday use (such as filling in bug information and opening new projects). Their support is second to none; a mail is normally replied within the hour; sometimes directly by phone.”
Ophir Amitai, QA Manager, Delek Corp.
“With PractiTest we finally connected Marketing, R&D and QA in one system, streamlining our whole product – development process – from requirements to testing. The results: shorter development and testing cycles, and a product that is closer to market demands.”
Uriel Perlman, Head of QA, Wavion
We open this month with the latest version of PractiTest, released on april 1st. This version includes new features and updates, most of them were requested by our customers.
Here are the main changes made in the latest version:
- Our new and improved Test Instances grid: You can now select to see any field taken from the original test (in the Test Library) as part of your test instances grid (within the Test Set). So you can now filter the instances in the grid based on the Test fields (just click on the Columns button)!
- Multi-level linked-lists: in previous versions, you were able to create linked-list field, whose values depend upon a previously created list field, so that your linked lists were limited to 2 levels only (parent-child). Now you no longer have to settle for a 2-level linked list, and you can create linked lists with as many levels as you need.
For example, you can create a regular list field to denote the OS you are working on, then a linked list of Browsers showing you only the browsers available for each OS, and then a second linked list of Browser Versions showing you only versions relevant for the selected browser.
- New notification list: users defined as Administrators can now add other users to an entity – notification list, to make sure their users receive messages when changes are made the entity
- Improved dashboard pie-charts, with easy to read labels located outside the different sections.
We hope you enjoy and benefit from these new additions, and as always, we are waiting for your feature request if you have further suggestions or comments, don’t hesitate to let us know!
We are happy to announce that PractiTest has been selected to participate in Red Hat Innovate.
Red Hat Innovate is a new initiative launched by Red Hat, the world’s leading Open Source Software Company. The initiative aims to assist innovative software development start-ups to build on the power of the open source community.
Red Hat – vote of confidence means a lot to us, and we are very excited to be offered this partnership. This opportunity will help us keep doing what we do best – developing and innovating in the field of software testing.
More and more teams are switching to Agile development, in order to increase their efficiency and meet the competitive requirements of the field and their users.
Agile software development is very different from more traditional forms of development. As such, it – only logical that adapting an Agile development methodology will require a change in the testing process.
Managing your Agile testing process using PractiTest
Agile testing is a team effort, and therefore requires high-quality communication between team members. Since the testing process may seem less “organized”, it – very important that the relevant information is available to all parties involved. You should always know what should be tested, who – testing what and where everything stands.
Here at PractiTest we are ardent believers of agile development and testing, and we try to design our test management software accordingly. Many of our features can contribute significantly to your agile testing process (as well as make your life a lot easier regardless of your testing methodology). Using Traceabiliy between entities, dynamic views instead of rigid folders, the flexibility of our customization settings, and the graphical information displayed in the Dashboard – your testing process can be more effective than ever before.
In more traditional testing methods, you would use the Requirements module to define how your system under test (SUT) should work, and what should be tested. In an Agile testing process, you can replace the traditional requirements with user stories – short and precise descriptions of your end users’ needs. You can then organize your User Stories using Custom Views.
Sharing tests in the test library
In PractiTest you can write and manage your Acceptance Tests (i.e. – tests designed to ensure that your requirements are met) within the Test Library, linking them back to the User Story where they originated.
You can then use the history, comments and notifications features to allow everyone to add their inputs into these tests, and to be informed about any changes made by other users.
You can simply create a test for each User Story, where developers can provide their inputs to testers as they come up with ideas during the design or coding process.
Creating tests sets for each user story
We recommend creating Test Sets for each User Story Independently. These test sets can contain the acceptance tests, functional tests, and any other testing operations needed for a specific User Story. This way you can get a better sense of coverage and completion for each User Story. It is also recommended to use the Tractability function to link between tests and their user stories.
Grouping issues based on their target sprint and user story
When you report issues, use custom fields to assign them the sprint in which they should be solved.
Also, in order to have tractability between issues, tests and requirements, you should link your tests to their relevant user stories. You can report issues directly from your test runs (using “fail and issue”), or link the issues back to the tests they originated from, for full tractability.
Using views to organize your issues based on Sprints, Users Stories, Modules, etc.
A good practice is to use the Issues Module not only to report bugs, but also to manage all the tasks of your User Stories and Sprint. Create tasks to keep track of the activities of your project and their individual statuses.
Provide visibility using a Summary Dashboard and additional Dashboards per User Story
You can use the Dashboard to keep your team up to date with the status of the Sprint in general, and of each User Stories in particular.
With the help of the views you have in each of your modules, create one dashboard centralizing all the information for your Sprint, and then create additional dashboard tabs with information for each User Story independently.
A couple of weeks ago we had a short service outing for PractiTest.
The service was down for about 22 minutes. This was the first time in over 18 months that our service was unavailable for more than a couple of minutes (and even this happened only twice) or as part of a scheduled maintenance.
Even though short outings like this one are common in our Industry (after all there is no system, not even Gmail, that doesn’t have glitches once in a while) we have gone through a serious retrospective analysis of what happened in order to avoid similar issues in the future, and maybe more importantly to respond even faster in the event something like this happens once again.
What went right
Part of our analysis showed that there were many things that worked correctly.
– We got both SMS messages as well as notification phone calls from our automatic monitoring systems telling us something was wrong with our servers.
– All back-up systems were working correctly (even though we did not really need them because no data was corrupted at any time).
– Our team was aware of the issue even before the first of our users contacted us.
Things to improve
We also detected a couple of things that need to be improved:
1. Because of system security procedures there were only 2 PractiTest employees who could respond and act when issues like this happened. Unfortunately this number seems to be not enough because at the exact time the issue happened one of them was commuting and the other one was also out of the office with a dead smart-phone battery.
To avoid issues like this we provided another employee with access to these servers. We are also creating an internal notification process to make sure that at least one of them is available 24/7 – with more than one way to communicate 🙂
2. Up to last week our internal monitoring system didn’t cover secondary services and one of such services turned to be the culprit. Now we’ll monitor all services, primary and secondary. This means that the monitoring process will give a head’s up before the services reach a dangerous level, so that we have more time to act.
3. One of the things we had already planned to do but may take a couple of sprints to have in place, is the ability to use the Autoscale system provided by Amazon. This will allow our system to automatically scale up in cases when the CPU of any of our services goes over a set threshold.
We already started working on this, but now we increased the development’s priority of it.
4. Last but not least, we want to provide even better visibility and transparency to what is happening in our service. We know that we have the best support and provide almost immediate answers via any of our current communication channels (e.g. Support Site, Skype, email, etc)
But we need to improve the way we broadcast information by being quicker with our twitter updates or by publishing blog posts such as this one faster and closer to the date of the incident.
(*) Just a short note to say that some of our technological plans may change as we have been accepted to be part of the Redhat Innovate program.
As always, we are here to answer any questions you may have about this or any other aspect of our service.
Please don’t hesitate to contact us via email@example.com.
The PractiTest team.
Just before the end of the 2011, and maybe as a starting point for 2012, we just released (this last Wednesday) and update to PractiTest with additional features requested by many of you during the last couple of months.
The feature list is extensive, but here is a summary of the highlights:
- User alert before leaving a page with unsaved data. A simple yet useful reminder for those cases when you “accidentally” left a page with issues or tests and you forgot save your work before hand.
- Multilist support on the dashboard. This feature will allow you to create graphs and tables also for fields of type multilist, providing enhanced visibility into your project.
- Added instance count field to the Test Set Grid. Similar to the Step Count in the Test Library, providing added visibility into your Test Sets
- Improved visibility into the users in your account. Showing Account Administrators a list of their users by the projects they are assigned to, and of the projects with all the users in them. This feature also allows you to delete users from all projects simultaneously.
- Email notification for users when added to a new project. Making sure your users are aware of new assignments or additional projects they can now access via PractiTest.
- And many additional smaller features and fixes
As always, we invite you to go to our User’s Feedback forum and update us with the features and options you would like to see included in PractiTest. This information is really important to us to make our system better and more aligned with your needs.
From all the PractiTest team and family, we hope you had a pretty cool and fun 2011, and we wish 2012 is you an event better year; a year of happiness, success & fruitful testing!
We’ve been working really hard on the “October-2011” version of PractiTest, that we released this Wednesday (today 🙂 ).
To be honest, we originally aimed to release this update about 6 weeks ago, but the scope of the features kept growing, and it took us more than expected to reach “code freeze”. Eventually, we decided to cut the scope a little and made this release as an opening shot for the next ones to come.
Here are some of the major items we included in this version:
- Better (ajax) grid in the Issues and Test-Instances. This grid comes with many requested features, such as:
- Batch edit & batch filter – also to Test-Instances
- Better and complete batch edit for Issues
- Batch delete where permitted
- Column chooser for the Instance Grid -> this means you can choose what columns you want to see in the instance grid, including custom fields
- and more
- Attachment support for steps – enabling to attachments (or links) to steps, and see them while you run the test.
- Better history log for step changes
- Adding comment to the ‘send by email’ feature of the issues
- a large number of additional improvements and bug fixes
We already started working on the next version, and always there are many things coming that have been asked for in our User Feedback forum. Still, we ask you to keep telling us what you’d like to see in PractiTest so that we can make the system even better for all of us.
Until next time (hopefully in a shorter time this time around)!
We've been making changes over the last several weeks to better support our customers at PractiTest. As our client-base grow, so do the support requests, and our need for more automation and integration to our workflows.
That’s why we have migrated to new PractiTest help platform (via Assistly). This will make support more efficient. What you can expect is the same level of support, with the following visible changes:
- All support will be answered right in your inbox.
- A new knowledge-base, with the same articles you're used to.
- Later on, an easier ticket submission right from the app instead of opening your email or creating a ticket in the help site.
We are confident this new system will make our excellent support even better.