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
{{ message }}
This repository has been archived by the owner on Oct 12, 2021. It is now read-only.
There are tons of unit tests that we inherited from jetpack:
find modules -type f -name "*.test.js"
There is also a testing framework available, that has atrophied a bit. We should go through all of these tests, and move the ones that are pertinent next to our source files. Having done this, there will be two types of automated tests in chromless, "high level" html tests that are complete applications (the stuff in tests/ right now), and low level headless javascript tests.
We shouldn't require all tests to be passing in order to close this issue, but should open separate issues for classes of test failures once this task is complete.
The text was updated successfully, but these errors were encountered:
A little brother to issue #65.
There are tons of unit tests that we inherited from jetpack:
There is also a testing framework available, that has atrophied a bit. We should go through all of these tests, and move the ones that are pertinent next to our source files. Having done this, there will be two types of automated tests in chromless, "high level" html tests that are complete applications (the stuff in tests/ right now), and low level headless javascript tests.
We shouldn't require all tests to be passing in order to close this issue, but should open separate issues for classes of test failures once this task is complete.
The text was updated successfully, but these errors were encountered: