- you can now test on development or production with testID set
- for android, this changes testID to use resource id instead of content description
- you no longer need to pass `--env.e2e`. e2e is simply usable if testID is set
- the `testID` property will also set `accessibilityIdentifier` and `accessibilityIdentifier` property will set `testID` only if there is a `testID` already set
BREAKING CHANGES:
`Application.orientation` is no longer a function.
Migration: Remove `()` from the `Application.orientation()` call:
```diff
import { Application } from "@nativescript/core";
-console.log(Application.orientation());
+console.log(Application.orientation);
```
`Application.systemAppearance` is no longer a function.
Migration: Remove `()` from the `Application.systemAppearance()` call:
```diff
import { Application } from "@nativescript/core";
-console.log(Application.systemAppearance());
+console.log(Application.systemAppearance);
```
* fix(android): nested frames were sometimes not recreated (#9748)
Co-authored-by: Eduardo Speroni <edusperoni@gmail.com>
* feat: testID property for use with e2e testing without interfering with a11y
* feat: better testID support along a11y
wip
* fix: make sure we have a defined id
* feat: --env.e2e to enable testID
* chore: return if using testID
* chore: cleanup
Co-authored-by: Eduardo Speroni <edusperoni@gmail.com>
Co-authored-by: Igor Randjelovic <rigor789@gmail.com>
Android accessibility services automatically announce the text itself as the description (see https://developer.android.com/guide/topics/ui/accessibility/apps#describe-ui-element)
If an a11y property is provided, the content description should also be set for TextView elements to keep the support for Labels/Buttons that only have a font icon as text and therefore need to have an accessibilityLabel.
Co-authored-by: Nathan Walker <walkerrunpdx@gmail.com>
closes#9588
