Please enable JavaScript.
Coggle requires JavaScript to display documents.
Simplisafe Regression Proposal (Requirements (Web regression testing to be…
Simplisafe Regression Proposal
Requirements
App regression testing requires 5 people working only on weekends, 4 times a month
No overlap or guidance over calls from their side
We could use weekday sync-ups for Web Testing to clarify doubts related to App testing - if they are ok
Have about 317 tests which have to be run on multiple versions of android and iOS devices
:warning: Some tests would need more clarity as details are not enough
:warning: SMS alerts related tests are there, will they work on Indian numbers?
:warning: Will need their hardware to initiate tests that require interactions with hardware
:warning: Not sure if the QA would need to work in multiple shifts
Web regression testing to be done on weekdays
Overlap required on weekdays
Can setup sync-ups on Mondays, Wednesdays and Fridays from 6:30 to 7:00 PM
Regression tests will have to be created
POC required to run regression tests on all browser
My understanding is that this is for benchmarking efforts required
(Assumption)Features to be tested on the Web would be similar to app
Model
Only QA
5 members for Saturdays and Sundays in App team
Check with Tarun on how multiple shifts are planned in support if required
3 members for Web team on weekdays
Rotation between App team and Web team members after 1 month of foundation phase
1-1 swap between App team and Web team on weekly basis
Pros
Knowledge sharing for better coverage
Team motivation
Cons
Working on weekends
QA incentivized
Tests being repetitive could demotivate engineers
Could propose automation for some tests
Large portion of the team is blocked from billing point of view since the assignment is for weekends
Quote higher rates for weekends to offset the cost
QA + Support
3 support + 5 QA split between 2 teams to cover 7 days of the week
Start with 1 Support + 2 QA for Web; and 2 Support + 3 QA for App
Rotation between App team and Web team members after 1 month of foundation phase
Pros
More cost efficient
Easier to have support people on weekends
Motivation risk due to repetitive testing reduced
Possibility of shared support model to ensure better billing for support folks on weekdays
Cons
Risk of using support people in testing
Could start smaller
Train support
QA to Support ration heavier on QA