Skip to content
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

Closed
novas1r1 opened this issue Apr 26, 2024 · 7 comments
Closed

[Mobile App]: Improve Testing Documentation (currently Google Doc) #809

novas1r1 opened this issue Apr 26, 2024 · 7 comments
Assignees
Milestone

Comments

@novas1r1
Copy link
Contributor

No description provided.

@ssandino ssandino changed the title Improve Testing Documentation (currently Google Doc) [Mobile App]: Improve Testing Documentation (currently Google Doc) Jul 30, 2024
@KarinBerg KarinBerg added this to the App v1.1.13 milestone Aug 9, 2024
@KarinBerg
Copy link
Contributor

Improved the content of the App Testing Guide. https://docs.google.com/document/d/1-y__kbnLX3KCHp2pdXhzq58rbMmnXwUI-Cirihy224o/edit?pli=1

@KarinBerg KarinBerg assigned novas1r1 and unassigned KarinBerg and novas1r1 Aug 9, 2024
@ssandino
Copy link
Member

Looking good! Is anything speaking against adding the content to a TESTING.md file on our Repo, so it‘s accessible to anyone?

@KarinBerg
Copy link
Contributor

Not sure about the test accounts. Maybe they should not seen by any Github user?!?

@ssandino
Copy link
Member

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. :.-)

@KarinBerg
Copy link
Contributor

@ssandino I don't feel good with making these test accounts public. I would prefer to keep them internally. Maybe in another private repo?

@ssandino
Copy link
Member

ssandino commented Sep 27, 2024

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?

@KarinBerg
Copy link
Contributor

Done with #912

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants