After becoming a freelance tester at Test IO, through passing the onboarding course, you'll have the opportunity to take on various tasks beyond bug reporting, allowing you to gain experience and increase your earnings.
These tasks are:
Bug Reporting: A bug on a website or app refers to a flaw or error that hinders its intended functionality, leading to unexpected behaviour, crashes, or incorrect outputs. This error is described in a bug form that aims to properly document and communicate software issues to Test IO's standards. This is the primary task of freelance testers with Test IO. While performing this task, submitting as many reports as bugs you find and all types of bugs in scope is possible. These bug reports are paid after the Team Leader accepts them, so there is no need to wait for customers to review them. The only restriction a test cycle presents is its scope, which is necessary, that you get to know before accepting to join the test. Discover further information through our article: ❝Bug Report Payout❞.
Bug Reproductions: If another tester has already reported a bug, you can't submit the same bug again. Instead, you can submit a reproduction to show that you encountered the same issue. Reproductions help identify affected environments and determine the severity of the bug. Positive reproductions indicate the bug is consistent, while negative reproductions show that the function works as intended on your device. Rules for reproduction attachments include a required screencast of up to 15 seconds, including the website's current date and URL. Discover further information through our article: ❝Reproduction Payout❞.
User Stories: A user story describes software behaviour from a user's perspective. User story testing confirms if it works as expected. User stories are short tasks like adding/removing items from a cart or applying promo codes. You can reserve up to 3 executions for 30 minutes. Once reserved, others can't claim it. User stories guide testing and have reserved, locked, or limited statuses. Discover further information through our article: ❝User Story Review & Payout❞.
Test Cases: Test case tests involve following predefined steps to ensure specific scenarios or processes can be successfully executed. Testers claim test cases during a test and perform each step accurately, providing necessary attachments and answers. Bugs encountered can be reported separately or linked to existing reports. Test case executions have a payout based on completed steps and bug submissions. Discover further information through our article: ❝Test Case Testing❞.
Bug Fix Confirmation: Bug Fix Confirmation is a process where testers verify if a reported bug is fixed or still present. To perform this task, testers must pass a course and meet specific criteria. To execute this task, testers follow the bug report, test the issue, and select the corresponding result, providing professional feedback and uploading attachments following our rules. Discover further information through our article: ❝Bug Fix Confirmation❞.
Bug Report Confirmation: Bug Report Confirmation is a task where testers verify and provide customers with additional information about a bug. To perform this task, testers must pass a course and meet specific criteria. To execute this task, testers follow the bug report, reproduce the bug, and select the corresponding result, providing professional feedback and uploading attachments following our rules. Discover further information through our article: ❝Bug Report Confirmation❞.
Special Projects Participation: Based on customers' demands, there are specific projects the tester can work on. To participate, testers fill out a survey to apply, and only those who meet customers' requirements are selected. Once chosen, testers receive project details via email and may communicate through Test IO's Discord server. Various project types are available, including hardware testing and performance testing. Discover further information through our article: ❝Project Onboarding❞.