I am having exactly the same problem. I am calling Accounts.createUser(… in jasmine one set of client integration tests. Other tests expect the user to not exist and everything is ok on the first pass (following meteor reset) but the user is still there on subsequent runs.
I was just about to post to the ‘help’ section when I saw your question. Did you find a clean solution to the problem?
Have you tried doing a beforeEach or beforeAll call in your tests? It works for me in my jasmine-server-integration tests (I know you’re asking about client tests, but this is all I got).
Running into the same issue here as well. I believe if you add the test helpers as Meteor.methods in your main app, you can call them from your client-integration test and they will do what you need. Perhaps the obvious, inelegant solution.
I tried adding a test-helpers.js file outside of jasmine’s server and client folders, but it didn’t seem to work, which might suggest that only the server and client folders are being recognized by jasmine/velocity. New at this too, so let me know if you’ve arrived at better solution.