Page Comparison

Warning

This page is no longer in use, for up to date meeting minutes please see here:

Note: From next week we will combine all GPS meetings into the Monday meeting.

Attendees: Liz, Jeri, Stella, Dave, Diarmid

There’s been some progress on the tests, but mostly we talked about pivoting our automation efforts towards the GAEN app.
We seeem to have converged on BrowserStack as the place to test, since we have fewest impediments there (compared to SauceLabs & Perfecto).
There are some major challenges with e2e testign with GAEN, but Diarmid’s view is that can can build some tests that validate about 60% of the end-to-end flow, and that these will be more valuable to PathCheck right now than GPS App automation.
A lot of the building blocks we need for this are the same as what we have already developed.
Initial sketch of a plan here
https://pathcheck.atlassian.net/wiki/spaces/TEST/pages/275021847/e2e+testing+for+GAEN+application?atlOrigin=eyJpIjoiYmMwNjJlNTg3NjQ5NGNmM2IzYjVjNjgzMzExMzNhNTUiLCJwIjoiY29uZmx1ZW5jZS1jaGF0cy1pbnQifQ
Next steps:
- Liz to engage with Dev team, understand their build pipeline (GAEN is different from GPS) and figure out how to integrate
- Jeri to get started with the GAEN app (probably on Android)m get familiar with it, and start with anything that’s not blocked on Liz’s work.
- Diarmid to get Dev team (John Schoeman) to provide input on the proposed test automation.
Also: Diarmid is rolling off the project. Dave will be leading on teh GAEN app & hence this automation effort. Stella will still be around to help out as needed.

Available test environments: updates from Stella:

BrowserStack & SauceLabs licenses in place
Perfecto is also back online - with a new URL https://safepath.app.perfectomobile.com/

“Hello world” Mobile test has made good progress (Liz):

Tech stack (Liz)

Assertion library is Jasmine, similar to Jest.
Outstanding tooling choices: webdriver vs. nightwatch vs. testcafe vs. cypress other options.
Not a priority to have aligned stacks between mobile app & Safe Places, as they willl have a completely separate set of test cases.
We are using webdriver with Appium, as we don’t believe other options work with Appium. Choice still wide open for Web / Selenium.

Next steps on Mobile Automation:

Test succeeds but still returns an error code: this is step #1
step #2: get an iOS “hello world” working.
Not yet automated into pipeline - step #3.
Then we could begin implementing basic test cases.
Liz also suggests we look at WDIO image comparison service & native app compare - screen comparison tools. Easy to set up & powerful. Jeri will have a look at this over the next week.

This week:

Other items (Deven):

Z Attack Proxy (ZAP) - can analyze Selenium tests & spot any insecure practices on the fly.
ZAP HUD, feedback to developers in real-time.
Deven has some training materials Stella will take a look at this.

...

Versions Compared