TRD: Outline Standards for Unit Testing #617
StephenRiosDev
started this conversation in
Technical Research Documents
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, our unit tests are quite verbose, and are written in a way that tests multiple pieces of functionality at once.
For instance,
selecttestsmenu's implementation of keydown handlers and selection by using manually fired keyboard events to attempt to manipulate the menu in order to test various features. This means that tests that do this test multiple features inmenudespite the fact that the test is supposed to be forselect, so we are not only testing multiple pieces of functionality, we are doing so across multiple components.This discussion is to define an agreed-upon standard to be followed by all engineers when adding or updating unit tests in the future to improve test quality, stability, and specificity.
Beta Was this translation helpful? Give feedback.
All reactions