| A | B | C | D | E | F | G | |
|---|---|---|---|---|---|---|---|
1 | Actions | Acceptance criteria | Responsibility | Progress | |||
2 | Priority | Done | % | ||||
3 | P1 | Create Q&A oriented knowledge base for the team - e.g. internal StackOveflow: All features mapping Errors mapping Compatibility matrix | QA %name% | 55% | |||
4 | P1 | Extend checklist: Cover missing Product's parts Cover negative scenarios Cover most valuable bugs flows Cover error flows | QA %name% | ||||
5 | P1 | Apply categories for Suites: Smoke, Sanity, Regression | QA %name% | ||||
6 | P1 | Select Test management tool (e.g. OneTestPad, TestRails etc) Define Test Runs process | QA %name% | ||||
7 | P1 | Create list of desired configurations: Browser/OS, Device/Platform, GEO location, App Setting | QA %name% | ||||
8 | P1 | More robust testing on mobile (to cover 60% of all users) Focus on "test on mobile" using Compatibility matrix Include throttlening/low connection cases to Smoke suite Focus on testing on device farm (at first, as POC at least) | QA %name% | ||||
9 | P1 | Bring SWAGGER doc back to relevance (or any other way to learn about APIs): Swagger - for Own APIs Number of endpoints for all others (+ some description) | Developer | ||||
10 | P1 | API tests (manual) | QA %name% | ||||
11 | P1 | Boost bugs replication and analysis process (dig deep into bugs reproducing + use jira labels) | QA %name% and Developer | ||||
12 | P1 | Clean up and define Jira labels (product areas) Create Jira dashboard using labels above | PM and QA %name% | ||||
13 | P2 | Environment load - number of user sessions at the moment, users connected | Developer | ||||
14 | P2 | Agree on how/when to Add test cases for new features (on requirements validation, during dev, during qa?) | PM and QA %name% | ||||
15 | P2 | API tests for Own API endpoints create manual cases | QA %name% | ||||
16 | P2 | Automation coverage for API tests | QA %name% and Developer | ||||
17 | P2 | Review Prority Bugs list to be added to Regression suite in checklist | PM and QA %name% | ||||
18 | P3 | Use "chaos simulation" in testing | QA %name% | ||||
19 | P3 | Automation coverage for extended checklist | QA %name% | ||||
20 | P3 | Test users up to 10: Admin, Group admin, LP creator, Group admin + LP creator, Regular unpreviledges user, Systems Admin (superadmin) Test Groups up to 5: Users from above are members or admins Create Persona profiles: test users with certain settings for testing and apply persona setting for Test Users from above | QA %name% and Developer | ||||
21 | P4 | ||||||