-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unit & Integration test investigation #791
Labels
testing
Related to testing
Milestone
Comments
would like to do this after #761 |
|
pmarsh-scottlogic
changed the title
Automated test investigation
Unit & Integration test investigation
Feb 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Take stock of automated tests. See what bits of code we cover and which we don't. You could use test coverage tools for this, but to be more comprehensive, look at tests titles.
Write a list of functionality that has not been tested. Then prioritise in order of what's most used, what's most likely to go wrong, etc. Write tickets to implement.
AC:
no code changes, therefore no testing needed.
The text was updated successfully, but these errors were encountered: