I understand what it does. I'm saying that it's a change in behavior from previous versions, and there was a lot of utility when it ran all the packages that are used by a particular application. Isopacks took a bunch of steps forward, but the changes to test-packages is maybe not one of them (imho). Having visibility of the tests run over the entire application was really useful for integration testing.
If we want to do an application integration test using tinytests, are we suppose to use the .meteor/versions file and copy each package from meteor/meteor/packages into the myapp/packages directory? Is that the recommended workflow that's being suggested? If so, I'll certainly try to make it work; but it seems quite a step away from what test-packages used to offer.