3

I stumbled upon following issue today while doing automated e2e tests on CI. My app uses 3 firebase login methods: email link, firebase and google.

During e2e tests I initially thought I'll use email link to log in, but this is not possible as app needs to go out into an email client and click on such link, so now I am blocked.

I was researching the docs to see if there was any e2e testing advice on this matter, but wasn't able to find a solution.

Is there a common solution to this provided by firebase? Or is the only way here to use email + password auth?

Ilja
  • 44,142
  • 92
  • 275
  • 498
  • Do you mean e2e integration tests? as opposed to manual tests? – bojeil Jun 19 '18 at 04:07
  • @bojeil automated gray boxed e2e tests to be ran on CI, not manual. Hence, using certain tool for this, so I don't think I'll be able to go outside scope of the app and click on email login link to auth :/ – Ilja Jun 19 '18 at 07:29
  • @Ilja, have you read this ?https://stackoverflow.com/questions/20959748/e2e-protractor-test-requiring-oauth-authentication – John Jun 20 '18 at 02:21

1 Answers1

1

I think the best practice here would be to split the process in your tests.

Test 1 would be, let's see if an e-mail was sent as a result of something happening in your detox test. So you click the button and do an API call to your server to see if it has send out an E-Mail. Or you configure your backend to deliver the E-Mail to something that you can query for the email, like Mailtrap or something similar.

Test 2 would be to see if your app can handle when someone opens that URL. To test this you need to fake such a URL in your backend and open it with detox. For this, you can use the device.relaunchApp, see the detox docs here.

Daniel Schmidt
  • 11,605
  • 5
  • 38
  • 70