How to Submit a Task for QA Testing

To maintain a smooth QA process, it’s important to follow a consistent workflow when sending tasks for testing. Below is the recommended process for developers.

• Use a QA branch (if available)
  
  • If the project includes a dedicated QA branch, it’s recommended to keep it up to date with the latest changes from the main development branch. This provides a stable environment for testers, free from ongoing updates or interruptions

• • After completing a task, you can record and share a video demonstrating the feature or fix while still on your development branch. However, in the task comments, make sure to mention that the functionality will be testable after the merge to the QA branch, which usually happens at the end of the day.

• Record a short demo video using Komodo

  • Once your task is finished (whether a new feature or bug fix), record a brief video walkthrough using Komodo, a browser extension for screen recording.
    
    

  • The video should be clear and focused, showing only the relevant change

• • After finishing the recording, Komodo will automatically open a new tab where you can copy the video link. Paste this link into the comments of the task in Plutio.

• • This approach gives the QA team visual context without needing a full written explanation.

• For static or visual updates, use a screenshot

  • If the change is purely visual (such as layout or text adjustments), a screenshot of the modified area is sufficient.

• • Upload the image directly in the task comments for the QA to review.

• Move the task to "Ready for Revision."

  • After adding the video or screenshot and commenting that the task is complete, move the task to the "Ready for Revision" column in Plutio. This is the queue that QA checks regularly throughout the day.

• • If your task is not immediately testable because it still needs to be merged into the QA branch, make that clear in your comment. For example:
    "Can be tested after merge to QA branch."

• • If your app does not use separate branches, you can simply indicate that it’s ready to test.

• Prioritize returned tasks

  • If the QA team finds an issue and sends the task back, prioritize it early in your workday.
    Quick revisions help maintain development flow and reduce QA bottlenecks.