FILE-13 - Add more test coverage

[gitstart]

What does this PR do?

• Add more unit test coverage
• Add more e2e test coverage

Issue reference

#50

Demo video/scrennshot:

Added unit tests for each component

Added E2E test for app

Added E2E test for WebUi mode

Demo E2E

https://www.loom.com/share/c1fa9d4d5cfd418badf6b4f0e93ad38d

Coverage snapshot

This code was written and reviewed by GitStart Community. Growing future engineers, one PR at a time.

[gitstart]

env for webui

• VITE_ROOT_DOMAIN
• VITE_METRICS_ORIGIN
• VITE_STATS_ORIGIN
• VITE_MODE_WEBUI

env for embed mode

• VITE_ROOT_DOMAIN
• VITE_METRICS_ORIGIN
• VITE_STATS_ORIGIN

[gitstart]

@guanzo this PR is ready for review

[juliangruber]

These new tests are great!

I'm just wondering about the stability of this project - will adding tests with this level of detail slow down the project, or speed it up?

[DiegoRBaquero]

Not really familiar with FE or its testing, but, a lot of these assertions seem to be just asserting what the code is telling it to be. If we define button to have a width of X why would it be Y on the test?

[gitstart]

Not really familiar with FE or its testing, but, a lot of these assertions seem to be just asserting what the code is telling it to be. If we define button to have a width of X why would it be Y on the test?

Thank you for the question. The test is of two kinds, an e2e test and a unit test The e2e test uses Puppeteer to ensure that the features work from end to end on the browser and no new additions break existing features. Same as the unit test. It ensures that it renders as expected with the appropriate parameters and that future additions would not cause breaking changes.