From b6f68a8e72957c1abffd94a2e449f7d1ad5036d3 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Mon, 25 Oct 2021 17:21:30 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 51 +++++++++++++++++----------------------- 1 file changed, 22 insertions(+), 29 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index af5f05ae..9a94db10 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -12,6 +12,9 @@ + + + AUTOMATED TESTING NEEDS: Acceptance "smoke" testing to ensure can release confidently "E2E" testing @@ -20,26 +23,26 @@ AUTOMATED TESTING must be runnable here or against devops Cypress will test e2e, can jmeter as well?? - Load / capacity / stress testing - Find problem areas - dev / pre-release - Have an idea what hardware can support what load of users - marketing/ support / sales - how far can it go before failure? - what is the maxium simultaneous users for a given hardware config - digital ocean can help with this as we can spin up progressively more peformant droplets and load / stress test them to know - Does it recover from failure? - Find prior unknown bugs that result in failure under stress - - Tools / links - https://www.digitalocean.com/community/tutorials/an-introduction-to-load-testing - jmeter - https://jmeter.apache.org/ - https://www.digitalocean.com/community/tutorial_series/load-testing-with-apache-jmeter - https://riptutorial.com/jmeter/example/27413/script-recording-with-the-blazemeter-chrome-extension - https://haquemousume.medium.com/multiple-user-login-using-jmeter-f1529247bbf2 - TODO: - Find out if jmeter can be used for smoke and stress testing or do I still need to use cypress for smoke tests - how to install cypress standalone and remove vuetify outdated one? + +todo: hard cap on report generation with a timeout setting exposed as global ops setting + Needs to return fail on timeout properly so client can state clearly what happened + needs to ditch all resources tied up on server + it appears it never stops churning away on devops at least, no timeout at all?? + + + +investigate: hard cap on appointments brought back controlled by client in settings otherwise unusable + ideally centered around current date + applies to month view + force user to filter by tags if too much, i.e. truncated result with error so they can see it was limited + +investigate: hard cap timeout on anything very time consuming like report generation, datalist queries, schedule etc + if a report ties up the server for more than XX seconds it should stop it adn return an error too big + can't have server churning when user abandons op + cancellable report job? + simultaneous users reporting?? + need stress / load testing setup to really get into this properly @@ -51,17 +54,7 @@ todo: two emails with change to reports to add and also cases regarding naming i todo: ops document where is the query timeout setting and how to adjust it for timeouts in long running queries? -todo: hard cap on appointments brought back controlled by client in settings otherwise unusable - ideally centered around current date - applies to month view - force user to filter by tags if too much, i.e. truncated result with error so they can see it was limited -todo: hard cap timeout on anything very time consuming like report generation, datalist queries, schedule etc - if a report ties up the server for more than XX seconds it should stop it adn return an error too big - can't have server churning when user abandons op - cancellable report job? - simultaneous users reporting?? - need stress / load testing setup to really get into this properly todo: should some things that were tagified be reverted back like in v7 due to reporting and other issues?