62 lines
3.6 KiB
Plaintext
62 lines
3.6 KiB
Plaintext
I think the best course from here is to pick through the UI and find if there is anything further worth testing due to it's uniqueness and fragility when refactoring.
|
|
honestly though this may be enough to move to the next stage
|
|
|
|
- Test that confirms the version of the server on the login page is as expected this is so that can be used to test a hosted droplet test server and will ensure it has been updated and correct new build is being tested
|
|
- Need a way to simplify testing local dev vs online, so can have two separate batch files and just run whichever one required so when release can test locally first then during deployment of installs test one final time on devtest
|
|
- also include the version to test against in the command line as well. Put it in the pre-data generation and erasure block so it just aborts right away without modifying anything. Maybe just looks at the login page itself
|
|
|
|
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-
|
|
From the olden times years ago:
|
|
|
|
|
|
|
|
|
|
|
|
todo: meter reading table click on item to confirm item page no other way to easily get id of unit metered unless create it or something
|
|
|
|
TODO: high priority grid sort and filter test that excercises *all* options and filter types
|
|
this one will be hugely important as part of regression test as it was a constant source of issues in v7
|
|
|
|
Service user features work
|
|
sb self contained and use standard test data because will also want to run without accounting prior
|
|
Inventory User features work
|
|
OPS featurs work
|
|
Data filters work
|
|
form customize works
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB2aWV3Qm94PSIwIDAgNTAwIDI0OS42IiB3aWR0aD0iNTAwIiBoZWlnaHQ9IjI0OS42Ij48Y2lyY2xlIHI9IjEuNSIgY3g9IjAuMzk5OTkzODk2NDg0Mzc1IiBjeT0iMCIgZmlsbD0icmdiKDAsIDAsIDApIj48L2NpcmNsZT48Y2lyY2xlIHI9IjEuNSIgY3g9IjQ5OC4zOTk5OTM4OTY0ODQ0IiBjeT0iMCIgZmlsbD0icmdiKDAsIDAsIDApIj48L2NpcmNsZT48Y2lyY2xlIHI9IjEuNSIgY3g9IjI0OS4zOTk5OTM4OTY0ODQzOCIgY3k9IjEyNSIgZmlsbD0icmdiKDAsIDAsIDApIj48L2NpcmNsZT48Y2lyY2xlIHI9IjEuNSIgY3g9IjAuMzk5OTkzODk2NDg0Mzc1IiBjeT0iMjQ5IiBmaWxsPSJyZ2IoMCwgMCwgMCkiPjwvY2lyY2xlPjxjaXJjbGUgcj0iMS41IiBjeD0iNDk4LjM5OTk5Mzg5NjQ4NDQiIGN5PSIyNDkiIGZpbGw9InJnYigwLCAwLCAwKSI+PC9jaXJjbGU+PC9zdmc+"
|
|
"data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB2aWV3Qm94PSIwIDAgNTAwIDI0OS42IiB3aWR0aD0iNTAwIiBoZWlnaHQ9IjI0OS42Ij48Y2lyY2xlIHI9IjEuNSIgY3g9IjAuMzk5OTkzODk2NDg0Mzc1IiBjeT0iMCIgZmlsbD0icmdiKDAsIDAsIDApIj48L2NpcmNsZT48Y2lyY2xlIHI9IjEuNSIgY3g9IjQ5OC4zOTk5OTM4OTY0ODQ0IiBjeT0iMCIgZmlsbD0icmdiKDAsIDAsIDApIj48L2NpcmNsZT48Y2lyY2xlIHI9IjEuNSIgY3g9IjI0OS4zOTk5OTM4OTY0ODQzOCIgY3k9IjEyNSIgZmlsbD0icmdiKDAsIDAsIDApIj48L2NpcmNsZT48Y2lyY2xlIHI9IjEuNSIgY3g9IjAuMzk5OTkzODk2NDg0Mzc1IiBjeT0iMjQ5IiBmaWxsPSJyZ2IoMCwgMCwgMCkiPjwvY2lyY2xlPjxjaXJjbGUgcj0iMS41IiBjeD0iNDk4LjM5OTk5Mzg5NjQ4NDQiIGN5PSIyNDkiIGZpbGw9InJnYigwLCAwLCAwKSI+PC9jaXJjbGU+PC9zdmc+"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
=====================================================================================================================================
|
|
Smoke test = quick test to ensure the most critical functionality is not broken
|
|
this is not so useful for us as the act of development involves many smoke tests on it's own
|
|
also we don't release often enough to need this kind of test
|
|
|
|
Regression test = extremely detailed test to ensure *all* functionality is working properly
|
|
this is the most useful test for us and the one to run before any releases
|
|
Assuming it takes an hour or two at the most to run that's perfectly fine before a release as a sanity check |