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 (22 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (601 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Examine the package.json file in the repository to understand how the engines field is structured, then modify the autochecker code to parse that field and filter the test versions accordingly.
Tech stack
javascriptnodejs
Domain
testingdevops
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.
1-3 hours
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.jspackage.json
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80