17 lines
821 B
Plaintext
17 lines
821 B
Plaintext
e2e testing strategy:
|
|
|
|
Only test critical parts of the system and in that, only those prone to failure.
|
|
things prone to fail are:
|
|
- Vuetify on an update
|
|
- ?
|
|
So excercise all form components will be a big help
|
|
|
|
No need to test everything, just the most critical aspects and enough to confirm they essentially work.
|
|
let the integration tests handle the failure modes, weird exceptional cases etc
|
|
|
|
For example one solid test that can make a workorder and fill in all sections will be sufficient for that as a smoke test.
|
|
No need to test every possible rule or unusual set of circumstances.
|
|
|
|
This is important because the test maintenance could end up eating up tons of time better spent on other stuff.
|
|
|
|
If a failure comes up in the wild can add a test for it then fix it and that will be most useful |