[Idea]: develop a project test runner #7
Labels
difficulty: 3
Likely to be challenging but manageable.
idea
Potential GSoC project idea.
priority: high
High priority.
tech: javascript
Involves programming in JavaScript.
tech: nodejs
Requires developing with Node.js.
Idea
Currently, stdlib uses
tape
. The goal of this idea is to migrate away fromtape
and develop a test runner in-house, similar to@stdlib/bench/harness
. This has long been on our TODO list and would allow us to have a simple test runner which is oriented toward stdlib conventions (e.g., we don't use most of the assertion methods intape
).Bonus points if we can migrate away from
istanbul
tonyc
orc8
; however, this may be tricky if we want to support older Node.js versions.Expected Outcomes
All unit tests have migrated to the in-house runner.
Involved Software
No additional runtime deps. Will need to consult
tape
as a reference implementation, along with our existing@stdlib/bench/harness
implementation.Prerequisite Knowledge
JavaScript, Node.js.
Difficulty
Intermediate.
Project Length
175/350 hours. The scope of this idea can be adjusted depending on availability.
Potential Mentors
@kgryte @Planeshifter @steff456
The text was updated successfully, but these errors were encountered: