Research Automated testing to form a testing architecture #105
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#105
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
related to issue Research Testing #81
I suggest that we create a linear framework, it is the most basic framework and suitable for small teams. It is built from the testers scripts for each test case. These scripts can be managed by a "master script" to run all the tests without manually start every script, the "master script" could also have the feature of creating an document to compare earlier results e.g. outputs.
Tests should be clearly defined and well-written, the order of which the tests will be executed should also be planned e.g. dependencies. Test plan and "master script" should be reassessed over time to ensure the correctness.
"Master script" is essential for regression testing.
This is a suggested starting-point for unit testing.
This is super good! we will use this as a base to form the initial architecture.