You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I'm not sure about this particular implementation. after_success looks like the wrong hook to run UI tests unless we just want to warn about failures. Not sure how that'd work.
The text was updated successfully, but these errors were encountered:
As you said, I don't think after_success is the right one to run those tests.
I would rather run them as a simple extra step in the script list of commands and then use after_script to download the results via gsutil.
There's a way to add the client secrets to travis, encrypting a file:
http://engineering.dailymotion.com/running-firebase-test-lab-on-travis-ci/
But I'm not sure about this particular implementation.
after_success
looks like the wrong hook to run UI tests unless we just want to warn about failures. Not sure how that'd work.The text was updated successfully, but these errors were encountered: