test-fixture
Copy test fixtures to a temp dir and get resolved file paths.
Why?
I am tired of writing these:
pathtmpdircallbackfsepath
EVERY DAY!
So, I got this.
Install
$ npm i test-fixture -D
Usage
// By default, it will use 'test/fixtures' dir.const copy resolve = // copy 'test/fixtures' to the temp dir;async { await console // '/<temp-dir>/foo.js'}
fixtures(...paths): {resolve, copy, install, root}
- paths
Array<path>
to define the root paths of the fixtures, which is similar as
Defines the root of the fixture
const path = const fixturesRoot = path path
...paths |
base (dir of test fixtures) |
---|---|
undefined |
test/fixtures |
'a' |
test/fixtures/a |
'a' , 'b' |
test/fixtures/a/b |
'/path/to' (absolute) |
/path/to |
'/path/to' (absolute), 'a' |
/path/to/a |
Actually, the base
is path.resolve('text/fixtures', ...paths)
Without copying
const resolve = // -> /path/to/<p>/a.js
.copy()
Using const copy resolve = await // -> /path/to/a.js
await copy(options?)
await copy(to?)
- options?
Object
- to?
path=
the destination folder where the test fixtures will be copied to. If not specified, a temporary directory will be used. - clean?
boolean=false
whether should clean the directoryto
ifoptions.to
is specified. - install?
boolean=false
whether should run npm install after copying
- to?
Copy the test fixtures into another directory.
// is equivalent to
resolve(...paths)
Resolves the paths to get the path of the test fixtures
After .copy()
ed, it will resolve paths based on the destination dir.
If not, it will use the base dir. But never use both of them simultaneously.
/path/to/<base>
|-- a.js
/path/to/<to>
|-- a.js
await install(options?)
- options?
Object
options ofnpminstall
Install packages in the working directory. If run after await copy()
, then it will install packages in the directory which fixtures copied to.
string
getter: root The fixture root /<project-root>/test/fixtures