...
We have some bugs raised now (mostly from Winjit). What flow do we want to use to handle these?
John S to Triage bugs & put them into the Trello board
We need a R4T status in the workflow - Diarmid/Stella.
Need to define how frequently builds will be pushed to Test. In 48 hours or so, we should get daily builds - Matt
Investigate moving iOS to AppCenter (Debug builds only; Release builds have to be loaded via TestFlight) - Matt
OK for some testing to work on Debug builds, as long as some testing happens on the Release builds before we ship - hence we still need some testers on TF. Current pattern is once a week on Thursdays.
Setting up new Guam environment for Pen testing (and probably also BugCrowd).
Who can help me with this?
Server set up
Apple TF & Google Test Group set-up.
Art & Sherif to help me with this. But uncertain whether it’s all going to work w/ GAEN entitlements.
Moving forwards with Whitesource…
Video on their free solution here: https://resources.whitesourcesoftware.com/product-videos/whitesource-bolt-for-github
Raises GitHub issues. Is that OK?
John to take a look at this.
Some specific technical queries:
Do we have an API spec for the GAEN servers (Verification & ENS)? I though Sherif shared a spec with me, but can’t find it. Needed for scale testing.
Matt to dig out Swagger doc.
How does the GAEN app interact with multiple user accounts on Android? Are keys, ENs etc. per-user or per-device?
Per-app install, exposures are unique
But keys are the same per-device
Do some testing & see where we stand. Our storage is Realm (per-App), rather than per-user.
Testability for Accessibility, customization, languages…
Very valuable to have an easy means to generate all possible screens in the app without having to drive full e2e flows.
Not supported today. Could be handled as a requirement.
Drive as a new requirement - drive conversation to agree reqs. John to create a Trello ticket.
Questions about language testing scope & responsibilities that also need to be characterized - Diarmid to consider further.
Scale testing the App’s local RPID store
Guam have offered to get hold of 20 or so phones, set them all up in close proximity, and leave for a week or more. Worth doing?
Edging into “research project” territory.
Probably worth doing
What’s the app actually exposed to here? (as opposed to the OS) - focus on this if possible.
Very large key files?
Connectivity problems with very large key files - restart etc.
Download processsing happens only max 10 times a day, and if it hits a failure will abort and only start again some time later.
Very large numbers of ENs (but hard to imagine this being more than 100 or so of these…)
Upcoming function changes…?
Customization - In App name now shipped. PM to decide what else we need to do for MN & others (colours etc.)
UX changes - Onboarding flow rework is now in the code. Will be in next build. Some other minor changes (e.g. an extra link).
Analytics - Just getting started, release plans etc., still to be defined.
What else? - Who owns QA for per-HD deliverables of customization? Should be QA for now…