We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've had a number of groups who end up with quite a bit more test set-up and tear down needs.
To these students I have recommended they add a central ./test-setup.jsand instruct mocha to load this file explicitly and first.
./test-setup.js
Things that move into this file are setting up globally used mock adapters, the enzyme adapter, and database setup/teardown tasks.
"NODE_ENV='test' mocha ./test-setup \"./server/**/*.spec.js\" \"./client/**/*.spec.js\" \"./script/**/*.spec.js\" --require @babel/polyfill --require @babel/register
// test-setup.js // with these and other hooks at the top-level. before(() => db.sync({ force: true }); afterEach(() => db.sync({ force: true });
The text was updated successfully, but these errors were encountered:
Sounds reasonable to me.
EDIT: though running database syncs before every test, even frontend / utility / other tests, feels a bit heavy-handed for me.
Sorry, something went wrong.
No branches or pull requests
I've had a number of groups who end up with quite a bit more test set-up and tear down needs.
To these students I have recommended they add a central
./test-setup.js
and instruct mocha to load this file explicitly and first.Things that move into this file are setting up globally used mock adapters, the enzyme adapter, and database setup/teardown tasks.
"NODE_ENV='test' mocha ./test-setup \"./server/**/*.spec.js\" \"./client/**/*.spec.js\" \"./script/**/*.spec.js\" --require @babel/polyfill --require @babel/register
The text was updated successfully, but these errors were encountered: