Formal evaluation and analysis of React/JS testing framework #184
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#184
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?
We need to evaluate and analyse what testing framework to use for JS/React.
Assigned a24julot to this.
Jest minimizes the need for external dependencies and requires little setup, making it easy to get started with testing. It enables developers to write simple, maintainable unit tests and is effective for regression testing, as it quickly detects changes in the codebase. By rerunning tests after modifying the code, developers can immediately verify whether everything is functioning as expected.
There are many libraries available for front-end testing. Jest stands out due to its ease of use, speed and features. It is highly popular, actively maintained and remains a relevant choice for modern testing. The reliability of tests written in Jest also allows them to serve as a form of documentation.
Mocha is another popular testing framework, but it requires more configuration and can be more complex to set up. With Mocha, developers must choose and integrate additional tools and libraries themselves, while Jest provides the essential tools and libraries the developer needs up front.
Jasmine is also an option, but it often involves a more complex setup. Additionally, handling asynchronous testing can be more challenging.
One of Jest’s strengths is the quality of its feedback. When a test fails, it provides clear and detailed error messages, pointing directly to the source of the problem. Jest also includes a watch mode that automatically reruns tests whenever changes are made to the code. This eliminates the need to manually restart tests and improves developers productivity by providing immediate feedback.
What I've reviewed:
The evaluation of JS/React testing framework.
Checks performed:
Verified information about Jest, Mocha and Jasmine.
Checked against our wiki standards.
Checked if recommendation fits the project setup.
Looks good, Jest has also already been added as devdependency in #163.
Side note: Could be good to update our testing wiki with Jest guidelines.