-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
[Mobile App]: Improve Testing Documentation (currently Google Doc) #809
Comments
Improved the content of the App Testing Guide. https://docs.google.com/document/d/1-y__kbnLX3KCHp2pdXhzq58rbMmnXwUI-Cirihy224o/edit?pli=1 |
Looking good! Is anything speaking against adding the content to a TESTING.md file on our Repo, so it‘s accessible to anyone? |
Not sure about the test accounts. Maybe they should not seen by any Github user?!? |
So, with these credentials, people would be able to login as recipients if they download the staging app (but they would still need an invitation, right?). It doesn't give them a login to the admin tool. I don't see a big risk, but what do you think, @novas1r1 and @MDikkii? Alternatively, we could hide the login numbers in GitHub and keep them in a separate file. But then again, it would be another file. :.-) |
@ssandino I don't feel good with making these test accounts public. I would prefer to keep them internally. Maybe in another private repo? |
If you prefer, then let's not make them public. I would say we just put the test account details in a Google Doc, which is protected but can be shared upon request. And all the rest in the README is fine. I think this is easier than using a separate private repo for the account details, which can be complicated due to GitHub’s rights management. In the README, we can mention that the details are available upon request instead of including the account details directly. What you think? |
Done with #912 |
No description provided.
The text was updated successfully, but these errors were encountered: