esperancaJS/QA-flow.md

## QA-flow.md

      
    Raw
  

              QA-flow.md
            
          
    QA Flow

A small sum up of what I think an effective and efficient QA Flow could look like
Steps :


- [DEV] Submit Changes
- [QA]  Review Changes                   < ┐
- [DEV] Fix Issues raised in the Review    ┘                      


(A list of changes or Issues with screenshots and small videos is submitted at each step)
Details:

General test suite

(on Chrome, Safari, Android and IOS)


When Signed out the in-page notice is visible and blog content isn't


Register works


Login works


When logged in, blog is visible and in-page notice isn't


Navigating to another website preserves logged in account


When Navigating to other blog posts the wallet is charged


When Treshold is reached and wallet stops being charged


Top Up Works


Duration

The cycle stays open until a final thorough review is successfully done.
This can be as quick as a single 30 min review or as lengthy as a 1 week cycle.
QA work:


General test suite (up to 1h)
Specific review (up to 10 min)

Periodicity:


Before Major Releases
When 'completing' one of many features needed for a Release