swarms/ideas/127-SOB-testing-process.md

Preamble

Idea: 127
Title: make testing process in SOB transparent and easy to contribute in 
Status: In Progress
Created: 2018-04-02

Summary

• make QA process in SOB team easy to understand and support for newcomers;
• in order to reduce time spent on regression testing automate main usecases;

Swarm Participants

• Lead Contributor:@churik
• Testing & Evaluation: @annadanchenko
• Contributor: @asemiankevich

Product Overview

Full and transparent QA process in Status Open Bounty team will help to involve new people into testing process more quickly (if needed) and provide developers with more info about what was tested in particular PR or in develop branch. Ideally process should be integrated with TestRail, but initially smoke check list should be defined and than automated. Hence this idea is placeholder for current and future iterations of improving QA process in SOB team.

Requirements & Dependencies

For now blocker for 1 full-walkthrough autotest are:

• Jenkins doesn't recognize xml reports and looks for them in wrong place after last refactoring. Problem is still investigating.

Minimum Viable Product v1

Goal Date: 2018-29-06 Actions needed for MVP v1 passed:

Documentation

• Tutorial video or docs about QA process in SOB team
• Basic use cases (smoke check list) are defined in TestRail

Involment

• one more QA can test SOB

End-to-end test (1 full walkthrough test for SOB)

• automate creating PR
• define function for merging PR
• define function for SNT transfer
• define function for signing transaction and confirming payment