Decide which unit testing framework to use and set it up

[lfilho]

Initial thoughts:

• Jest for unit testing and main driver
• Playwright for driving a browser and actually testing the extension -- I read somewhere recently that an extension can't be tested headless, so we would need a headful driver.
  • This might impact our ability to automatically test the extension via CI, meaning the automate tests would have to run in a developer's machine, or in a more expensive CI setup (one with a X / window manager available so we can install and run full browser in there)

[lfilho]

Remember to update eslint config when decided: https://eslint.org/docs/user-guide/configuring#specifying-environments

[lfilho]

e2e testing (playwright or similar) is too big of a scope for this ticket. I have created another one to tackle that in particular: #38 .
In this one, I'll focus on unit tests only.

And for unit tests, I decided to go with Jest -- merely for having experience with it and having a nice CLI interface. :)

[lfilho]

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on:

• v1.1.0
• GitHub release

Your semantic-release bot 📦🚀