.meteor/versions file is unstable when using test driver pkg without adding it

[aldeed]

From the Meteor 1.6 changelog:

You can now run meteor test --driver-package user:package without first running meteor add user:package

Well, yes, but there's a problem.

Expected

When I run meteor run and then run meteor test --driver-package user:package, my .meteor/versions file should not change.

Actual

meteor test command adds the driver pkg and its dependencies to .meteor/versions. Conversely, meteor run command removes them.

So everything works, but in a project with many maintainers doing git commits, the versions file keeps flipping back and forth (test pkgs added, then removed) depending on whether each person ran the app or the tests last, prior to committing.

Workarounds

Pretty simple. Either manually adjust the versions file before committing, or keep the test driver in the packages list as was done prior to 1.6.

Since the only real workaround is to not even use the feature, I'd consider it a non-feature. :)

Solution

IMO, it should be fine to not update the versions file when running tests, if the driver pkg was never added.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.