In order to ensure the extension's functionality and compatibility with multiple sites and browsers, end-to-end testing should be integrated using Cypress. At least 3 initial tests should focus on the extension's functionality on sites where content is static and the Shadow DOM/Virtual DOM/Web Components are not being utilitized. Other tests should cover situations where the text on the site changes as the user interacts with it (Twitter feed, for example) and sites that utilize the Shadow DOM, React (non-SSR), Vue (non-SSR), etc. Proper test coverage requires ensuring compatibility with several of the most popular frameworks for developing front-end applications.
Problem
WIthout proper testing in place, the extension's functionality is not dependable. Updates may break certain features, and having a testing framework in place is a good way to prevent breaking changes.
Next Steps
[x] Install Cypress
[x] Init Cypress folders
[ ] Build tests for static sites
[ ] Build tests for interactive sites
[ ] Build tests for sites using the Shadow DOM and other Web Components
[ ] Build tests for sites using React
[ ] Build tests for sites using Angular
[ ] Build tests for sites using Vue
[ ] Build tests for sites using Svelte
Notes
If you are interested in completing a pull request for this issue, please tag @arimgibson to get approval first. This ensures that multiple people aren't working on the same PR at the same time, and helps to make sure you get credit for your work.
Description
In order to ensure the extension's functionality and compatibility with multiple sites and browsers, end-to-end testing should be integrated using Cypress. At least 3 initial tests should focus on the extension's functionality on sites where content is static and the Shadow DOM/Virtual DOM/Web Components are not being utilitized. Other tests should cover situations where the text on the site changes as the user interacts with it (Twitter feed, for example) and sites that utilize the Shadow DOM, React (non-SSR), Vue (non-SSR), etc. Proper test coverage requires ensuring compatibility with several of the most popular frameworks for developing front-end applications.
Problem
WIthout proper testing in place, the extension's functionality is not dependable. Updates may break certain features, and having a testing framework in place is a good way to prevent breaking changes.
Next Steps
Notes
If you are interested in completing a pull request for this issue, please tag @arimgibson to get approval first. This ensures that multiple people aren't working on the same PR at the same time, and helps to make sure you get credit for your work.