My testing processes could be better at catching bugs before code is merged into main.
I want to ensure that code pushed to main is bug-free because, eventually, code pushed to main will be automatically deployed into production.
⚜️ Any ideas on how to solve it?
Write a list of generic manual tests to do for each new feature. e.g. test it when signing in with a new nickname, test it when already signed in, etc.
🦄 Later: Solving it
💠 The problem
n/a
💠 The method
[x] In the task template, include the following testing items in the requirements section:
[x] New nickname
[x] Existing nickname
[x] Browsers: Firefox and Chrome
[x] Platforms: Desktop and mobile
[x] Ensure that each item is listed in dot-points so I don't have to tick each test for every task
darcydriscoll
commented
2 years ago
🐏 Now: Motivation
⚜️ Where's the issue?
My testing processes.
⚜️ What's the issue?
My testing processes could be better at catching bugs before code is merged into main.
I want to ensure that code pushed to main is bug-free because, eventually, code pushed to main will be automatically deployed into production.
⚜️ Any ideas on how to solve it?
Write a list of generic manual tests to do for each new feature. e.g. test it when signing in with a new nickname, test it when already signed in, etc.
🦄 Later: Solving it
💠 The problem
n/a
💠 The method
💠 Notes