You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It gets pretty boring pretty fast when for every change we make to our application we run through a mock registration to make sure our application still works. Instead what we should do is test the behavior of our UI components.
Ideally what this would look like is I can run a test that will go through the registration process for me and make sure that whatever behavior we expect to see in RegistrationView occurs when we specify an interaction with it.
Things we should test for are:
Display of front end validation
UI changes due to back end validation
UI changes due to successful registration
and probably many, many more.
For this particular task we should limit our scope to just the RegistrationView, but ideally we would do this for each of our front end views.
It gets pretty boring pretty fast when for every change we make to our application we run through a mock registration to make sure our application still works. Instead what we should do is test the behavior of our UI components.
Ideally what this would look like is I can run a test that will go through the registration process for me and make sure that whatever behavior we expect to see in
RegistrationView
occurs when we specify an interaction with it.Things we should test for are:
and probably many, many more.
For this particular task we should limit our scope to just the RegistrationView, but ideally we would do this for each of our front end views.
Some resources that might help with this include:
If anyone else has recommendations on what we should use feel free to edit this issue description :)
The text was updated successfully, but these errors were encountered: