2025-07-21
Test execution
- Fixed: if a class was annotated with an
@Ignoreannotation there was a small chance a shard would fail with theNo tests!error.
@Ignore annotation there was a small chance a shard would
fail with the No tests! error.AndroidJUnitRunner ran more tests than expected error when using the test storage service and targeting specific test classes.ew-cli version to 0.12.5.timeout message.
--dns-override $host=$ip option to ew-cli to override DNS resolution for a specific hostew-cli now passes proxy configuration to wireguard exit node, fixes ew-wg-exit-node timeout when using the egress tunnel featurehttps://emulator.wtf/o/<orgUuid>/r/<runUuid>/t/<className>/<methodName>.
You can use the test details URL as a base to construct URLs like this for linking to specific testcase results directly.timestamp attribute in <testsuite> elements.ew-cli version to 0.12.1.secretEnvironmentVariables, for use with things like
tokens, credentials, passwords, etc.secretEnvironmentVariables were not passed to the emulator correctly and had no effect.FileAlreadyExistsException wg-exit-node.edb0f9de race condition when using the egress tunnel.--secret-environment-variables, for use with things like
tokens, credentials, passwords, etc. These will be passed to the test runner in the same way as --environment-variables,
but won’t be visible in the emulator.wtf UI. Alternatively, secrets can be passed in via environment variables having
the EW_SECRET_ prefix, e.g. EW_SECRET_foo=bar.--test-runner-class.--help.ew-cli. Read more about the egress tunnel
here.INSTALL_FAILED_NO_MATCHING_ABIS error message so it’s clearer which dynamic library
could be the culpritChanged the default test result link visibility to private
NOTE: this affects new accounts only, we did not retroactively apply the new default to older accounts
assemble task no longer triggers emulator.wtf tests