You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although there are multiple tests present in the 1.test.js file when the command node --test is run only one of the tests is checked and run... even then the test fails 😱
It might be worth splitting the tests up over multiple different js files so that they can be run indivdually with the npm run test:# command as well as the node --test command.
It might also be worth looking into your package.json file and amending the script for running a test as currently it isn't running one.
The text was updated successfully, but these errors were encountered:
it might also be worth to add a proper script, so that it is easier to run the tests, at the moment it looks like this "test": "echo \"Error: no test specified\" && exit 1",
whereas you'd want something like this, especially if you split the tests into separate files: "test": "node --no-warnings --test", "test:1": "node --no-warnings test/1.test.js" "test:2": "node --no-warnings test/2.test.js"
etc.
This will make it easier for you to read the test output
Hey everyone,
Although there are multiple tests present in the 1.test.js file when the command node --test is run only one of the tests is checked and run... even then the test fails 😱
It might be worth splitting the tests up over multiple different js files so that they can be run indivdually with the npm run test:# command as well as the node --test command.
It might also be worth looking into your package.json file and amending the script for running a test as currently it isn't running one.
The text was updated successfully, but these errors were encountered: