QA Funnel Report

Objective

To see if the funnels are behaving the way they are supposed to.

Approach

After speaking with Tim about the context of the Objective and gaining background info, we mapped out the different approaches a user can take through our system in both signing up and re-signing up.

We adapted and modified the spreadsheet currently in circulation so that we could perform our ownfully independent analysis.

Test Results of Re-sign-up Scenarios

1 of 9 CORE funnel use cases passed
2 of 8 Event Page funnel use cases passed
3 of 8 Premium funnel use cases passed
5 of 7 Rankings funnel use cases passed

Effect on Funnel Reporting

13 Instances of a duplicate stripe ID made
7 instances of duplicate records in the database

Instances Of Incorrect Status

4 Instances in deactivated status
3 instances in pending status
1 instance in cancelled status
2 instances of the username being erased from the database (cannot reproduce consistently)

All of the following should have been in "activated" status, but were in an incorrect state when verified (after an hour waiting period to account for automated code).

Each Funnel Acts Differently on re-sign-up

CORE Funnel creates a new record in the database and a new record in stripe
Live event funnel creates a new record in stripe
Premium and Rankings funnel update the same record in the database and stripe

Test Results Spreadsheet

https://docs.google.com/spreadsheets/d/1Sfibg505h0JPLT0w07i-6be8ERZj4LjAtBueOHvusJs/edit#gid=1725234481