SpencerCDixon/redux-cli

Implement an in memory file system to use in testing

Open

Aperta il 20 set 2017

Vedi su GitHub
 (1 commento) (0 reazioni) (0 assegnatari)JavaScript (886 star) (63 fork)batch import
2.0good first contributionhelp wantedtesting

Descrizione

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

Guida contributor

Tech stack
javascriptnodejs
Dominio
clideveloper experience
Tipo issue
test
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
2
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Node.js testingfile system mockingredux cli repository structure
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
60
Direzione di ricerca
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.