I need to make a change to the meteor build tools to support slightly different api.export flavors. It’s a simple change, but unfortunately it’s not something I can monkey patch.
How can I run meteor self-test “package-tests.*” ?
When I try this, I get the following error:
self-test is only supported running from a checkout
UPDATE: Looks like all I need to do is run ./meteor self-test
Ok, so running a specific meteor package test (ex. ./meteor self-test “show release” --slow) results in the following:
Calvins-MacBook-Pro:meteor calvinfroedge$ ./meteor self-test “show release” --slow
package-tests: show release …
… fail!
=> wrong-exit-code at …/…/…/…/…/tools/tests/package-tests.js:1813
=> Expected: 0; actual: 1
=> Last 100 lines:
2| => Errors while publishing:
2|
2| While pre-publishing package test:1opdpr:
2| error: Match failed
2|
package-tests: show release w/o recommended versions …
… fail!
=> wrong-exit-code at …/…/…/…/…/tools/tests/package-tests.js:1973
=> Expected: 0; actual: 1
=> Last 100 lines:
2| => Errors while publishing:
2|
2| While pre-publishing package test:1j8l2x:
2| error: Match failed
2|
Skipped 145 non-matching tests (don’t match specified pattern)
2 failures:
Is the test harness broken? This happens with no changes applied.