Testing with ember-cli

[alvincrespo]

I'm trying to find documentation on how to get ember-simple-auth to run fine in our tests. Unfortunately I'm having an issue where if I simulate the login experience, the mechanism for authentication keeps it around in the next test.

For example, If in test 1 I test the user can view the login page, and then test 2 is to testa successful login, then test 3 fails because I test whether you can register, but you are already logged in.

Is there something I can do in the qunit teardown to remove the session/token?

[seriousben]

For that purpose, I use the ephemeral store:
ember-simple-auth-session-store:ephemeral
When testing. So that on the app.destroy the store stops existing and the
user is not logged in.

We also fake authentication for authenticated test by using:

var session = App.__container__.lookup('ember-simple-auth-session:main');
session.set('isAuthenticated', true);
session.set('accessToken', 'authenticated');

[alvincrespo]

@seriousbenat360pi Thanks for your help on this!

I'm curious how I may be able to set ember-simple-auth-session-store:ephemeral during testing when visiting http://localhost:4200/tests in ember-cli? Would reopen or reopenClass do something like that?

[seriousben]

Good question, to do this I have a check in the initializer app.get('testing')... unfortunately we could not change the simple-auth initializer once its loaded and we could not inject another store either.

[marcoow]

Yes, changing the store after setup isn't really supported - checking whether you're running in test env on startup is the way to go for now. Just as a heads up: in the next version all configuration will be removed to window.ENV['simple-auth'] so that you can change it depending on app state in a cleaner way without having to change the initializer (which will in fact go away).