mobly
mobly copied to clipboard
E2E test framework for tests with complex environment requirements.
`AndroidDevice#log_path` is not always created, but it's accessible by user code. This is ok most of the time because `logcat_service` is usually used. --- This change is [](https://reviewable.io/reviews/google/mobly/848)
Currently, Mobly won't clean requested resources if receives a SIGTERM signal. We can use a simple test to reproduce the bug: ``` import logging import os from mobly import base_test...
I can follow [Mobly101](https://github.com/google/mobly/blob/master/docs/tutorial.md) to execute `$ python hello_world_test.py -c sample_config.yml` without issue. But when I updated `hello_world_test.py` to register SL4J service as below: ```python from mobly import base_test from...
Our Linux build status on `README.md` is still linking to the old Travis CI which we don't use any more. Let's update this with status from the current CI system.
This may just be a question of me not being able to find it in the docs/examples, but: In our use case we run the bulk of our testing in...
So it can be easily applied to a whole function.
This came up in a discussion with @winterfroststrom The `AdbProxy` was designed for the most straightforward use cases, like `adb.shell('getprop')` - simple call and return. This does not work well...
Right now, java side exception's stacktrace and description are merged together and thrown as a single msg. `snippet_client` should be able to separate the two and report them better.
Most adb calls issued by `AndroidDevice` don't have any timeout today. This is causing problems in large device labs where there is a diverse collection of devices. Sometimes devices get...