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
To augment our continuous integration and deployment as we move towards production, we need to make sure we don't break the codebase as we go. Some testing implementation is necessary to ensure that the full application functions as designed.
I think the ideal pathway here is to first have a few tests that answer questions such as:
Does the homepage render correctly?
Are specific elements on the page available?
These tests would likely have to run outside of the renderer (e.g., spin up the dev server, hit some test urls, parse and make assertions over the html output).
Once we have this basic level of QA, we can start testing more detailed elements (individual components) and adding more detailed tests (is CSS doubled? are initial loads optimized and quick? etc.)
The text was updated successfully, but these errors were encountered:
To augment our continuous integration and deployment as we move towards production, we need to make sure we don't break the codebase as we go. Some testing implementation is necessary to ensure that the full application functions as designed.
I think the ideal pathway here is to first have a few tests that answer questions such as:
These tests would likely have to run outside of the renderer (e.g., spin up the dev server, hit some test urls, parse and make assertions over the html output).
Once we have this basic level of QA, we can start testing more detailed elements (individual components) and adding more detailed tests (is CSS doubled? are initial loads optimized and quick? etc.)
The text was updated successfully, but these errors were encountered: