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.
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.
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 help page.
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.
The PractiTest Team
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!
“Thanks for a great product!”
Michele Williams, Core Apps
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
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.
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.