Project Tasks

Need to get some more structure around the project especially after initial release.

- [ ] CI/CD (for e2e tests, integration tests, longer tasks that should not be run while developing but should fail on PRs)
- e2e tests
- cypress.io OR puppeteer OR selenium
- integration tests
- Jest / Mocha / etc. 3rd Party Service Connections
- misc
- ?
- [ ] Project Version Control
- npm preversion task (unit tests, audits, linting, etc)
- npm postversion task (github tasks, [chrome webstore deployment](https://github.com/IBM/publish-extension-webpack-plugin))
- [ ] Githooks
- Pre-Push hook to run preversion npm task above

Could use some help planning the structure of this out from another set of eyes. Also needs to be added to the contributing guide when complete.

Start by reviewing the existing npm scripts and the contributing guide, then map the proposed CI/CD, end-to-end, integration-test, versioning, and pre-push-hook work. The issue is complete when the project structure and tooling choices are agreed, the workflows are implemented, and the contributing guide documents them.

Written by the indexing model from the issue text.