1# CarSettings Multivalent Tests
2
3Unit test suite for Settings, SettingsLib with device and deviceless
4capabilities either using Robolectric (or Ravenwood).
5
6## Why Multivalent
7
8There are called multivalent because the same tests can run in mock SDK or real
9device/emulator SDK. Writing tests once and being able to run using different
10SDKs help eliminate duplication and flakiness.
11
12Deviceless tests run faster and are more stable. They provide more reliable and
13quick feedback during development and help catch any regressions early.
14
15## How to run
16
17To run the multivalent Robolectric tests.
18
19```
20$ atest CarSettingsMultivalentRoboTests
21```
22
23To run the multivalent Device tests.
24
25```
26$ atest CarSettingsMultivalentDeviceTests
27```
28