Testing: Create tests for Temperature #156
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#156
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?
Tests for Javascript
In the wiki(test guidelines) it mentions that we should not create tests for the front end components. Isn't the javascript all front end? I'm unsure what should be tested, if it can be clarified.
Made unit tests for useTemperature.js. I made these with reacts test library, but they should be made with jest to avoid further dependencies. Will try to fix this.
Is this issue still relevant? Does the tests still work?
We agreed to not test frontend stuff, which basically means all the stuff that can be interacted with by the users in localhost. This ultimately means that we are not testing HTML elements via end-to-end testing, but we are testing API fetching and everything that is not HTML and CSS.
I made the tests but it was agreed that they may be unnecessary, I am not sure if my branch was deleted or not, but the tests were finished and working, testing the states when API worked and did not work.
All right, I'll close this issue but we will keep the tests in the code as an example of how to create tests for API states (if ever needed).