Testlio values quality over quantity. This has been our motto from the beginning and it expands to everything we do. We also expect our community of expert testers to respect it while they are working with us. We have listed down actions that show us that a tester might not be able to deliver a quality we are looking for. As transparency is very important for us, we wanted to communicate unacceptable actions to everyone.
We have categorized the actions that are not tolerated in our community into groups based on their severity and resulting actions.
Group 1 actions will result in immediate offboarding from our community.
Group 2 actions will initially result in a written warning. After three warnings the tester will be off-boarded.
Group 3 actions are with slightly lower damage, but still not acceptable. In these cases test lead, someone from QA or Community team will contact the tester. If similar cases become more frequent we might lower testers’ pay rate, amount of projects they are eligible to work on or give them a warning.
Actions and behavior not tolerated in Testlio community:
- Using someone else’s Testlio account or letting someone else use your account for testing.
- Distributing private information about Testlio or its clients.
- Using test data with offensive or unprofessional content.
- Start testing too late in the cycle and letting this affect testing quality as a tester is not able to test the whole task list with the remaining time.
- Posting ghost issues (empty issues with only titles) only to fill them out later.
- Marking cases as “Passed” or “Failed” when they are actually not testable (should be marked as “Unable to test”).
- Marking cases as “Passed” or “Failed” without actually validating them first.
- Showing one client data on another one’s cycle.
- Expressing unprofessional comments about the client or the related app in the project app or anywhere on the platform.
- Not following the privacy guidelines – mentioning client names publicly, sharing client-specific sensitive data.
- Not informing your test lead or QA manager when you encounter issues that prevent you from testing or delivering good results.
- Engaging in the personal belittling of anyone in the community.
- Accepting an invite but not showing up to a test cycle (without a valid reason).
- Not fully following the task lists, focus points, out-of-scope notes.
- Not following the exact steps when reproducing issues.
- Adding a video to the report that is corrupted (file does not open), that has a really bad quality (video is too blurry, shaky, hard to see and/or too long) or adding an irrelevant video (does not show all the steps or shows totally different things).
- Testing for longer than assigned time and expecting to get paid for those hours without confirming it with a test lead beforehand.
- Not specifying a proper reason when marking a case as “Unable to test”.
- Commenting issue as 'is reproducible' though it's actually not reproducible and vice versa.
*These lists are subject to change.
Please note that we do not take any quality issues or the resulting measures lightly. We will communicate with the tester beforehand to see what led him/her to take the actions and are often ready to give our testers a second chance, as long as the mistakes haven’t been intentional or malicious.