SpencerCDixon/redux-cli

Implement an in memory file system to use in testing

Open

#104 opened on Sep 20, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (886 stars) (63 forks)batch import
2.0good first contributionhelp wantedtesting

Description

Let's reduce the dependence on writing and reading actual files during tests.

It should be reasonably straight forward to translate the tests to mock-fs or similar library. And streamline the tests for reading rc files and blueprint directories

Contributor guide

Tech stack
javascriptnodejs
Domain
clideveloper experience
Issue type
test
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.js testingfile system mockingredux cli repository structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
First, examine the existing test suite in the redux cli repository to identify tests that read or write to the file system (e.g., tests for reading rc files and blueprint directories). Study the mock fs library API to understand how to create an in memory file system. Then, systematically replace each file IO operation in the tests with mock fs equivalents, ensuring the test logic remains unchanged. Finally, run the full test suite to confirm no real file system access occurs and all tests pass.