-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP Documented acceptance testing #409
WIP Documented acceptance testing #409
Conversation
Related to #349 |
Awesome @binhums 💃 |
This could maybe do with being defined through the blueprint
+1 |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
1 similar comment
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Going to squash and merge this into another branch to clean it up (CLA errors are due to my own email being misconfigured on github) |
Any plan to add this? Also needed would be auth mocks. |
Any updates? |
🚨 Do not merge, work in progress 🚨
First steps towards setting up a standard practice for acceptance testing with EmberFire. This should include:
Progress:
Potentially out of scope:
Notable considerations:
N.B. merging into branch
acceptance-testing
cc @tstirrat