impress/impress.js

Test coverage for all plugins

Open

#659 opened on Jan 15, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (38,178 stars) (6,605 forks)batch import
good first issuehelp wanted

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 with a title like "Add tests for plugin pluginname"

Related: #657

Contributor guide

Tech stack
javascript
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScripttesting framework knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Review existing test files in src/plugins/ directory for structure. Check the related issue #657 for context. Create a new issue for each plugin, focusing on core functionality tests. Use the existing test setup to write at least one test file per plugin.