From 465f0ac4f991f83f8e728359d10d7df9e6c67aef Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 4 Nov 2021 23:19:40 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 89 +++++++++++++++++++++++----------------- 1 file changed, 52 insertions(+), 37 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 0ceffd85..ad5e2036 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -7,49 +7,65 @@ "Make it happen" - Jim July 28th 2021 -## TODO TO BETA -AUTOMATED TESTING - NEEDS: - CYPRESS: Acceptance "smoke" testing to ensure can release confidently "E2E" testing - After code changes need compliance test that everything is still working - must be end to end so that all aspects are tested as much as possible - must be runnable here or against devops - Cypress will test e2e - ## E2E TESTING - Cypress dashboard free self hosted alternative if I need it: https://docs.sorry-cypress.dev/guide/get-started -todo: create e2e "supersmoke" test that excercises *all* of AyaNova - not enough to just open pages and look for elements, that's not catching if server is involved beyond serving the app pages - Step1 create a unique naming variable prefix for all testing data so can run over and over - Sets itself up with what it needs, assumes as little as possible pre-existing - Must create unique records, maybe including logins - Must create every type of record possible then re-open and verify they exist - Schedule will benefit from having made a findable workorder to then look for in month / day view - Reporting? - At the end of the day it must be a acceptance test we can rely and and also to add bug issues to that are then fixed to detect regressions +OUTSTANDING MAJOR AREAS TO BETA +- Known important issues prioritized for v1 and beta + testing issues + my misc issues below + triage v8 cases, move to priority 2 or implement them all at this point + this will constitute the freeze on new features when get to here, only stuff in the list and bugs will get done +- Features + Customer workorders + Customer CSR something?? + dashboard widgets + Reports (stock) + FREEZE POINT ON NEW FEATURES (aside from plugins / add-ons) + v8Migrate completed + trial / seeder system + docs + +- Installer + + + +OUTSTANDING BEFORE RELEASE +- Beta testing completed +- Plugin / addon replacements implemented and fully tested + qbi + qboi + ??? others?? +- Regression tests completed and ready to use *before* release so we can add issues to it as they come up and test reliably +- Rockfish licensing finished up + lots to do there but enough for trial and sales for now in existing is enough + one license redundant route also should be baked into initial release even if it points to same place for now +- Biz decisions + pricing + licensing + hosting + + + + + + + + + + + + - -todo: load / soak test over the weekend? - - - -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 -Prioritize items to get to beta fast as possible - make an official to beta list of items and even if others are there they can wait todo: two emails with change to reports to add and also cases regarding naming in light of removing unitmodel number field for consolidated name field some viz fields have old names / reports need updating @@ -63,13 +79,6 @@ todo: should some things that were tagified be reverted back like in v7 due to r TRACK: - - - - - - - Customer work order form / view / open??? Customer CSR form has a bunch of todo in the template, WTF? Dashboard / widgets @@ -414,6 +423,8 @@ todo: 3 Schedule form reporting? |_____/|______|_| \_\ \/ |______|_| \_\ +todo: 1 saving workorder overwrites address manually typed + todo: 1 seeding - seeded vendors should be tagged with type i.e. Shipping, Supplier whatever replaces the old vendortype property so trial users can make sense of it todo: 1`don't log user logins in INFO level, move down to debug or trace @@ -477,6 +488,10 @@ todo:2 errors are inconsistent some use "error" some use "code" to mean the same todo: 2 Should the database integrity check run as a regular job? because a person could fuck up the db while the server is running and the server wouldn't notice until it tried to access a fucked up table +investigate: 3 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 NOW ....