admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Checkpoint before removing cypress (attempting)

Browse Source
This commit is contained in:
John Cardinal
2021-10-28 23:03:29 +00:00
parent b2e2f396bf
commit c2961c3563
1 changed files with 20 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
ayanova/devdocs/todo.txt
View File

@@ -13,14 +13,6 @@
todo: add code for client reporting to handle a busy response
perhaps it retries after the delay a fixed number of times then reports back a fail / retry later to the user
joyce suggested a folksy message regarding server busy, something friendly and non techy sounding
I'm thinking people would not see this message very often hopefully
AUTOMATED TESTING AUTOMATED TESTING
NEEDS: NEEDS:
CYPRESS: Acceptance "smoke" testing to ensure can release confidently "E2E" testing CYPRESS: Acceptance "smoke" testing to ensure can release confidently "E2E" testing
@@ -28,12 +20,29 @@ AUTOMATED TESTING
must be end to end so that all aspects are tested as much as possible must be end to end so that all aspects are tested as much as possible
must be runnable here or against devops must be runnable here or against devops
Cypress will test e2e Cypress will test e2e
## E2E TESTING
todo:2 cypress testing for load testing etc
has to be done manually, there is a good idea in the comment here:
https://stackoverflow.com/a/51197403/8939
basically, init a new vue ui project, commit it, then add e2e plugin then recommit to see what all changed so can then manually remove that from main project
Look at moving to a standalone Cypress setup, why bother with the one built into vue ui, it doesn't seem to offer any benefits to doing it alone
this way can be fully up to date etc
https://www.cypress.io/
Remove from vue ui project but make copy of tests first
then make new project folder for this and put the tests there
install standalone cypress and go it without vue stuff
todo: soak test over the weekend?
todo: discuss with Joyce reporting requirements and if we are at the stage to be making any real world reports yet todo: discuss with Joyce reporting requirements and if we are at the stage to be making any real world reports yet
- stripped down bare reports with as little extra elements on page as humanly possible (as per dashboard UI advice guy) - stripped down bare reports with as little extra elements on page as humanly possible (as per dashboard UI advice guy)
- let the user add any elements if they want them, we want as white a page as possible in our stock reports, clean, simple, no extra bits anywhere - let the user add any elements if they want them, we want as white a page as possible in our stock reports, clean, simple, no extra bits anywhere
- Reports, where it's at and about muted style for them
style from dashboard design principle book where every non essential item is a distraction (table grids etc)
also would prefer monchromatic with just a tinge of color if any
@@ -55,8 +64,6 @@ todo: two emails with change to reports to add and also cases regarding naming i
some viz fields have old names / reports need updating some viz fields have old names / reports need updating
todo: ops document where is the query timeout setting and how to adjust it for timeouts in long running queries? todo: ops document where is the query timeout setting and how to adjust it for timeouts in long running queries?
todo: should some things that were tagified be reverted back like in v7 due to reporting and other issues? todo: should some things that were tagified be reverted back like in v7 due to reporting and other issues?
@@ -65,10 +72,7 @@ todo: should some things that were tagified be reverted back like in v7 due to r
TRACK: TRACK:
Reports, where it's at and about muted style for them
style from dashboard design principle book where every non essential item is a distraction (table grids etc)
also would prefer monchromatic with just a tinge of color if any
@@ -579,18 +583,8 @@ todo:2 many biz objects are not using new PUT methodology
might be that they don't need it but for consistency should check into it might be that they don't need it but for consistency should check into it
## E2E TESTING
todo:2 cypress testing for load testing etc
has to be done manually, there is a good idea in the comment here:
https://stackoverflow.com/a/51197403/8939
basically, init a new vue ui project, commit it, then add e2e plugin then recommit to see what all changed so can then manually remove that from main project
Look at moving to a standalone Cypress setup, why bother with the one built into vue ui, it doesn't seem to offer any benefits to doing it alone
this way can be fully up to date etc
https://www.cypress.io/
Remove from vue ui project but make copy of tests first
then make new project folder for this and put the tests there
install standalone cypress and go it without vue stuff
TODO: Need stress test for client that can generate workorders in parallel for load testing
######################################################################################################################## ########################################################################################################################
######################################################################################################################## ########################################################################################################################