This commit is contained in:
2020-04-04 21:08:18 +00:00
parent c020ab0362
commit 12caccf2b2
2 changed files with 12 additions and 6 deletions

View File

@@ -50,12 +50,6 @@ CURRENT TODOs
@@@@@@@@@@@ ROADMAP STAGE 2:
todo: is there a way to not have to specify "name" 5 times in a text field on widget form (for example), maybe can use this.ref??
- Yes, but it involves wrapping the v-text-field into my own component
- Then I can pass name as the ref and the component will handle the rest
- However, this is not a super bad idea because it adds abstraction above vuetify, but then really how realistic is it to just swap out vuetify?
todo: add tests for the following:
- customize form form
- NOTE: All cypress tests run serially anyway, so it's perfectly ok to customize the widget form, go see if it worked, then come back and reverse it without affecting the other tests

View File

@@ -0,0 +1,12 @@
e2e testing strategy:
Only test critical parts of the system and in that, only those prone to failure.
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