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
Have you read the CONTRIBUTING guide on posting bugs, and CODE_OF_CONDUCT?
yes I read the things
This issue exists in the latest tap version
I am using the latest tap
Description
Hello
I'm starting to learn tap, and the before/after config is important for me (I spin up an API server)
I found an edge case when using the --changed flag; if the previous tests all passed, Tap will not re-run the tests if the configuration file, or any before/after script has changed.
console.log("log before tests");// throw new Error("gotcha");
src/modules/search/foo.test.ts
importtfrom"tap";t.test("this is a child test",(t)=>{t.pass("whatever");t.end();});
bash
yarn test ./src/modules/search/*
Step 1:
run the bash command, and let the tests succeed
Step 2:
un-comment the throw error in beforeTest.ts
Step 3:
run the same bash command, the tests will skip and not throw any error
Step 4:
change anything in the test file, and run the same bash command. since the test file has changed, the tests will be run again and the error from the beforeTests.ts will finally show
Is there an existing issue for this?
Have you read the
CONTRIBUTING
guide on posting bugs, andCODE_OF_CONDUCT
?This issue exists in the latest tap version
Description
Hello
I'm starting to learn tap, and the before/after config is important for me (I spin up an API server)
I found an edge case when using the --changed flag; if the previous tests all passed, Tap will not re-run the tests if the configuration file, or any before/after script has changed.
Reproduction
package.json
beforeTests.ts
src/modules/search/foo.test.ts
bash
Step 1:
run the bash command, and let the tests succeed
Step 2:
un-comment the throw error in beforeTest.ts
Step 3:
run the same bash command, the tests will skip and not throw any error
Step 4:
change anything in the test file, and run the same bash command. since the test file has changed, the tests will be run again and the error from the beforeTests.ts will finally show
Environment
The text was updated successfully, but these errors were encountered: