Test coverage for all plugins
- Dominant language
- JavaScript
- Stars
- 38.2k
- Forks
- 6.6k
- PR merge metrics
- No merged PRs in 30d
Description
As of this writing, the core impress.js API has ok test coverage, as does the navigation plugin. All other plugins were essentially implemented without tests. (Sorry, historical reasons.)
Now that they're merged to upstream impress.js though, we do have a goal of adding test coverage for all of them. Basically, it would be nice to have at least one `src/plugins/pluginname/pluginname_tests.js` file for each plugin.
This is a catch all ticket. If you want to help in creating tests for a plugin, please [file a new issue](https://github.com/impress/impress.js/issues/new) with a title like _"Add tests for plugin pluginname"_
Related: #657
Contributor guide
No contributing guide indexed for this repository
Research direction
This is a catch-all issue rather than a plugin-specific task. Start by choosing one plugin and inspecting its src/plugins/pluginname directory, using the existing core API and navigation plugin coverage as references. Done means the selected plugin has a src/plugins/pluginname/pluginname_tests.js file; file a separate issue for that plugin as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100