getify/asynquence

contrib: break out tests into separate files for each plugin

Open

#36 opened on May 29, 2014

View on GitHub
 (6 comments) (0 reactions) (1 assignee)JavaScript (1,739 stars) (156 forks)batch import
help wanted

Description

In addition, bundle.js needs to optionally include a test only if building with the plugin in question.

Contributor guide

Tech stack
javascript
Domain
testingbuild system
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.
1-2 days
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
JavaScriptasynquence plugin architectureNode.js build process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Review the current test structure in the asynquence repository, particularly how tests are included in bundle.js. Examine the plugin directories to understand the existing test files. Check issue comments for any additional requirements or decisions. Implement separation of tests per plugin and update bundle.js build logic to conditionally include test files based on the plugin being built.