onivim/oni

Add more tests

Open

#1,128 opened on Dec 14, 2017

View on GitHub
 (11 comments) (1 reaction) (0 assignees)TypeScript (336 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (11,389 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Couldn't find an issue directly addressing this, but it would be pretty nice, if not essential, that there's a good testing framework for making sure that changes do not regress the code. I understand that while the code is still in flux testing does not matter that much, but given that there is already quite a rich and working feature set, it'd be a shame if it became buggy.

Personally, I think Jest is the best testing framework in this context because of its integration with React components. Have to admit I haven't used it myself, though.

Contributor guide

Research direction
Examine the current test setup in the repository, understand the components that need testing, and write Jest tests for them, focusing on React components.
Tech stack
typescriptreactjest
Domain
frontendtesting
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScriptReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65