1. Exploratory Testing
Having the freedom to explore all the sections of a piece of software allows going through happy flows as well as edge cases. It’s important, however, to follow the testing instructions in order to gain a clear understanding of what the scope of a testing cycle is and report only relevant issues as a result.
Testing can be accomplished by using design specifications, such as provided use cases, or through functional specifications. These specifications might include everything from integrations and user screens to user commands and data manipulations to business processes and searches. The test specification document provides a detailed view of what should and should not be tested, as well as additional pieces of information aiming to provide a smooth and valuable testing experience.
💡 Here are six fundamental principles of exploratory testing:
- Reading the test specifications while familiarizing yourself with the software;
- Identifying the expected functions of the software;
- Interacting with the features of the software;
- Comparing the actual results of your interaction with the features to the expected results;
- Evaluating whether the software works as outlined in the test specifications;
- When the software doesn’t perform as expected, describe the issues encountered as detailed bug reports.
2a. Test Case Execution
- The email invitation to the test case execution includes testing time frames, selected environment (device/OS), and payment for completing the test;
- In order to ensure a smooth experience, we recommend replying to our invitation as soon as possible letting the team know whether you are available for the test;
- It’s important to read all the test instructions and to clarify any unclear aspects ahead of time, in order to meet the agreed deadlines;
- If the behavior encountered in the app doesn’t match the expected outcomes written in the test case suite, the affected test cases are “Failed” and relevant bug reports must be attached to the test case execution document;
- The test case execution is considered complete once all of the test cases inside the selected suite have the appropriate status assigned to them.
2b. Automated Test Case Execution – Tester Work Platform
- The Tester Work profile includes notifications about upcoming and ongoing tests
- Successful tests are the ones where the instructions have been thoroughly followed
- Being aware of the time left to execute a set of instructions allows stress-free testing
- The desired outcome of a test case execution is having all of the relevant notes and proof for the issues encountered during that execution.
3. Usability projects (UX)
Having a bug-free and perfectly polished product is not always enough for success, there is also emphasis on the importance of a great design and how user-friendly an app is. Usability surveys are meant to gather valuable user feedback about a certain app or system. Based on the received information, the creators of the product will be able to determine what features to focus on next and to improve them in a way that it will offer a more enjoyable experience to the end-user.
Usability tasks can be standalone projects, but they are often considered the sequel of a functional exploratory or test case execution cycle. Basically, this means that the testers are asked to test the product thoroughly first and then they have to fill out a survey including questions about the application.
When filling out the usability survey, these are the most important criteria to think of:
- Offer review only about products you are familiar with
- Provide valuable and honest answers - these are the most constructive
- Strive to provide comprehensive and grammatically correct feedback
- Focus on the scope of the usability test while completing the survey
Also, check out our video about the Tester Work testing types!
Article is closed for comments.