Specify and execute tests.
Is the test basis for specifying tests missing? Don't have a good tool for creating test cases? Does test execution take a lot of time? Does the reporting of defects not happen in the tool you test with? Then it's time to explore Testersuite!
Use a good testing tool!
If you are a professional tester then we don't need to explain the added value of a testing tool. Whether it is about specifying test cases or running tests. Or to capture test results and quickly register test findings. For this, you obviously want to use a user-friendly tool so that you can work quickly and have everything neatly together.
There is no solid foundation for testing
An important prerequisite for specifying test cases is a good test basis. For example, in the form of requirements, user stories, workflows or functional designs. The test basis describes the desired operation or design of, for example, custom software or standard applications. By testing, the desired operation must be demonstrated.
When you are asked to specify test cases, you naturally start by looking for the test basis. Then it often turns out that there is no good test basis, or even worse, that the test basis is completely missing. Because the test object is soon to be delivered, there is no time left to prepare and deliver the desired test basis. For better or worse, you then go about specifying test cases anyway...
Testers should of course be involved much earlier in the process. So that they encourage the creation of a test base suitable for specifying test cases. Of course, this common problem is not going to be solved just by using a tool like Testersuite. However, it does help when the test basis is defined centrally. For example, in Testersuite you can create requirements and link them to the test objects they relate to.
Experience for yourself the ease of capturing and using a good test basis in Testersuite .
Specifying test cases is laborious
In practice, Excel is widely used for specifying test cases. This makes sense because most organizations have Excel available, most employees are familiar with it, and it is a highly flexible tool. It is therefore an excellent tool for creating logical test cases and breaking them down into test steps. Or, for example, for creating a test case matrix based on the data combination test. However, there are also limitations when tests are developed in Excel.
If you want to build a test suite that’s easy to maintain, it’s wise to define the test cases as “building blocks” for process or chain tests. In Testersuite , it’s possible to combine test cases into test scenarios. A test case is then used in multiple test scenarios. If you try to achieve this using linked Excel files, the test suite quickly becomes very labor-intensive and confusing.
For traceability, you naturally want to link the test cases to the test objects or requirements they pertain to. When test cases are created in Excel, it becomes very complex to establish relationships with the test objects and/or requirements being tested. In Testersuite , you specify the test cases directly alongside the test objects or requirements they belong to.
You’ll often want to link files or screenshots to test cases or test steps. These attachments must be available when executing the test cases. This is very simple in Testersuite , but very difficult in Excel.
In short, Excel can be a great tool for specifying test cases at first. However, if you want to build a well-structured and easy-to-maintain test suite, import the test cases created in Excel into Testersuite and enrich the test suite with test scenarios, attachments, and relationships to test objects and requirements.
Testing and recording of results is cumbersome
After test cases have been defined, the tests are executed by testers. If the test cases are created in Excel, the test results must be recorded in those same Excel files. For a small number of tests, this is still quite manageable. However, when there are more tests—and business testers are also involved—recording test results quickly becomes very time-consuming and error-prone.
The solution to this is to separate the specification and execution of test cases. In Testersuite , you can easily create test runs with the test cases that need to be executed. While running the tests, you can specify the result at the test step level. In addition, a tester can attach files or screenshots to the result of the test step. And if the result of a test step is NOT OK, you’re immediately given the option to create a test finding for that specific test step.
Experience the ease of executing test cases in Testersuite!
Registering defects is time-consuming
Recording test findings during testing is often very time-consuming. You want to provide a clear description of the actions performed, the expected result, and the actual result. In addition, you usually want to add and edit screenshots. All of this is done to ensure that the person responsible for resolving the defect can reproduce the issue.
In Testersuite , recording test findings is very simple. While running the tests, you can immediately create defects . The test case, including the test steps, is automatically added to the defect . Additionally, the test object or requirement to which the defect relates is automatically entered into the defect . The tester can immediately paste screenshots from the clipboard and edit them in Testersuite.
Experience for yourself how easy it is to record defects in Testersuite. We’d be happy to show you how this works.
What our customers say...
"We used Testersuite for the release of our ECD. This helped ensure that testing was carried out efficiently and that the results were reliable."
"The implementation of the Edu-V appointment system is complex. We test data exchange with educational service providers and schools, and have successfully completed two releases. Without Testersuite , this would not have been possible."
"Even users who do not test regularly can easily work with Testersuite and execute test cases effectively."
"A clear and simple way to convey what testing is"
"Testersuite is very user-friendly and intuitive. You can work with it almost immediately"
"With Testersuite you get a grip on the situation and stay transparent. For me, that's the biggest win."
"By using Testersuite , it is traceable in which test step something goes wrong."
"Testersuite is a tool that is easy, intuitive and no nonsense to use."
"As a tester, you can put everything you need into the test case build of Testersuite."
"In Testersuite everything is registered centrally. Now we no longer have to search for everything together across numerous different systems."
"Testersuite provides structure, creates insight, portability and control over the testing process."
"The approachability and ease of use of Testersuite is the way to bring non-IT people into the testing process."
"Our test-automation tool was not ideally set up. We rectified that by starting with Testersuite, among other things."
Powerful functionality
Tips for getting started
