| commit | 1edf94eaa5e079c69c11885b56d94d47a1f637b9 | [log] [tgz] |
|---|---|---|
| author | Manish Mandlik <mmandlik@google.com> | Wed Jun 23 20:18:25 2021 -0700 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Jun 30 16:34:26 2021 +0000 |
| tree | b3420378f8b09456f3871e5d4171b2a53bff4087 | |
| parent | 47755ea120a4fe355195288d302b22cef57f9c28 [diff] |
Revert "bluetooth: Add Advertisement Monitor pattern filter tests"
This reverts commit ffd483109ae4a7676be44556b82c23d59cdbda69.
LE_SCAN_FILTER_DUP flag was enabled on all platforms earlier. So, tests
involving RSSI filter were disabled earlier when HW offloading is not
available as host may receive as little as one adv during passive
scanning. This test was created just to focus on patterns filter without
any RSSI filtering to verify working of pattern matching with multiple
monitors, multiple clients and suspend/resume scenarios.
This test is no longer required since we are now disabling filter_dup
for background scanning and RSSI filtering will work for SW based
filtering as well.
BUG=b:175746099, b:187375746, b:169375729
TEST=Run AdvMonitor test batch on both devices with HW offloading
available and not available.
Change-Id: Icf72c404058d6818eec47677cab2a4b773d6400f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2984465
Reviewed-by: Yun-Hao Chung <howardchung@chromium.org>
Reviewed-by: Archie Pusaka <apusaka@chromium.org>
Tested-by: Manish Mandlik <mmandlik@chromium.org>
Commit-Queue: Manish Mandlik <mmandlik@chromium.org>
Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.
Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:
A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.
A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.
Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.
Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.
Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.
See the guides to test_that and test_droid:
See the best practices guide, existing tests, and comments in the code.
git clone https://chromium.googlesource.com/chromiumos/third_party/autotest
See the coding style guide for guidance on submitting patches.
You need to run utils/build_externals.py to set up the dependencies for pre-upload hook tests.