Minor changes, make the page more readable
saucelabs provides pre-built hardware and software with browser/mobile versions etc.
Dattaz : curiosity
Differences between what Matthieu and Isaac do
automate the most common user journeys : open the app, open a page, etc
BDD frameworks : given, when, then (natural language)
Opinion : little point to have common code between all the repos.
Java unit tests works well, but do not allow to interact with the system (permissions, SD card etc)
Image-based testing : not recommended for us
Which content to use for the tests? Ray Charles archive allows to test some aspects, but not all of them.
Careful about the multi-lingual aspect.
Step by step : start with something simple to test, and see what needs to be improved.
Android pains : different storage locations, onboarding
Levels at Google :
0- no tests1- at least one test, and CI that runs it2- policy : team that agree that, at every change, a procedure must be 3- coverage : minimum 40%
The code coverage is not a primary measure, but can indicate a trend on code quality attention by developers
But too much unit tests can be complicated to maintain.
Feature coverage can be another measure.
What we're not going to do in the short term for Android testing :
For the short term : use preferably Espresso and/or UIOtomato for Android testing.
Choice for Android testing (by the end of the week) :
No tests on kiwix desktop for now. Maybe for kiwix-serve?