There are no tests/ no test strategy yet

[nvh95]

Now, jest-preview hasn't had tests for its source code. So whenever we add a new feature, we just update the demo code at /demo then see if our new code works with the demo. This strategy does not scale if the number of features increases in the future. Also, we are not confident that old features are getting broken.

So, we need to find a test strategy to maintain the quality of code and help to build new features by TDD.

[nvh95]

Idea: e2e strategy.
Just have an example that has many CSS strategies (App.test.tsx), then assert if they are rendering correctly.

• snapshot
• explicit asserting

[nvh95]

TODO

• To run all tests in examples folder
• Can we leverage it