victorb/autochecker

Read versions to test based on package.json engines

Open

#5 opened on Apr 13, 2016

View on GitHub
 (1 comment) (2 reactions) (0 assignees)JavaScript (601 stars) (22 forks)batch import
enhancementhelp wanted

Description

Right now, if no arguments are provided, autochecker will test in all available versions.

Instead, it should read the engines key in package.json and figure out which versions that have to be tested.

Contributor guide

Tech stack
javascriptnodejs
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
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
Node.js basicspackage.json engines field
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
First, examine the current codebase to see how version lists are determined. Look for files that parse package.json or iterate over available versions. Modify the logic to read the engines field (e.g., engines.node) and only test versions that satisfy the range. Consider using a semver library for range matching. Test with sample package.json files.