[TECHNICAL] QA variant

[jesmrec]

In order to make easier automation tasks, it would be helpful to create a new variant in the project, called test, testing or similar.

Now, when some authentication methods are supported in the same server (Bearer, Basic), by default the app takes the safer one (Bearer). So, if OAuth2 and OIDC are available, they are selected by default and Basic is the fallback option.

The new variant should do the opposite. In case basic auth is available, basic should be used by default and most prior. Only that change, the same as Release variant if posible. With this change, autom test will avoid jumping to the browser, getting rid of an annoying dependence of the available version and preventing the context change and the driver loading.

Also, it'd be interesting to remove scoped storage, so that it's posible to handle local files for actions and assertions.

So, these are the interesting changes for a testing release:

• Welcome wizard disabled
• Release notes disabled
• Basic auth by default in the app
• Scoped storage disabled
• Screen protection disabled

Is this feasible?

TASKS

• Research (if needed)
• Create branch technical/testing_variant
• Development tasks
  • Create new flavor
  • Disable welcome wizard
  • Disable release notes
  • Disable screen protection
  • Set basic auth as default login method
  • Disable scoped storage
• Code review and apply changes requested
• Design test plan
• QA
• Merge branch technical/testing_variant into master

[michaelstingl]

Check MDM options in the iOS app for inspiration

[jesmrec]

Brandable option is valid too.