Create wiki for the testing architecture #194
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#194
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?
Needs a description and brief explaination of the testing architecture, we also need to add the diagram.
Finished Writing a wiki page for the testing architecture. It's not a guide or documentation on how to create tests but a guide for the general structure of how we want to make tests and the scope of them
The documentation is clear and provides a strucutred overview of testing, especially regarding unit and regression testing. The use of xUnit and Jest is well motivated and the guidelines for unit testing (min, max, invalid data) are useful and practical.
However, I would suggest a description of how different parts of the system interact from a testing perspective, for an example how frontend test, backend and mocking are connected (if they are) and how they work together within the testing architecture.
Apart from that are the documentation well described and easy to follow!