| /external/llvm/unittests/Support/ |
| D | ArrayRecyclerTest.cpp | 53 ArrayRecycler<Object> DUT; in TEST() local
56 Object *A1 = DUT.allocate(Cap, Allocator); in TEST()
60 Object *A2 = DUT.allocate(Cap, Allocator); in TEST()
64 Object *A3 = DUT.allocate(Cap, Allocator); in TEST()
75 DUT.deallocate(Cap, A2); in TEST()
84 Object *A2x = DUT.allocate(Cap, Allocator); in TEST()
87 DUT.deallocate(Cap, A2x); in TEST()
88 DUT.deallocate(Cap, A1); in TEST()
89 DUT.deallocate(Cap, A3); in TEST()
93 Object *A3x = DUT.allocate(Cap, Allocator); in TEST()
[all …]
|
| /external/autotest/server/site_tests/network_WiFi_ReconnectInDarkResume/ |
| D | control.DisconnectAfterSuspendSameAP | 15 This test verifies that the DUT that suspends connected, then subsequently
18 network that appears during suspend is the same network that the DUT was last
23 1) AP ("AP 1") is brought up, and DUT connects to it
24 2) AP 1 is brought down, disconnecting the DUT from it
25 3) Another AP ("AP 2") is brought up, and DUT connects to it
26 4) DUT suspends while connected to AP 2
27 5) AP 2 is brought down, disconnecting the DUT from it while suspended
29 7) The DUT is woken from suspend
30 8) Verify that the DUT is connected to AP 2 upon resuming from suspend
32 We verify the connectivity status of the DUT on resume by parsing shill logs,
[all …]
|
| D | control.DisconnectBeforeSuspendSameAP | 13 This test verifies that the DUT that suspends disconnected successfully
16 the DUT was last connected to before suspend.
20 1) AP ("AP 1") is brought up, and DUT connects to it
21 2) AP 1 is brought down, disconnecting the DUT from it
22 3) Another AP ("AP 2") is brought up, and DUT connects to it
23 4) AP 2 is brought down, disconnecting the DUT from it
24 5) DUT suspends while disconnected
26 7) The DUT is woken from suspend
27 8) Verify that the DUT is connected to AP 2 upon resuming from suspend
29 We verify the connectivity status of the DUT on resume by parsing shill logs,
[all …]
|
| D | control.DisconnectAfterSuspendDiffAP | 15 This test verifies that the DUT that suspends connected, then subsequently
18 network that appears during suspend is different from the network that the DUT
23 1) AP ("AP 1") is brought up, and DUT connects to it
24 2) AP 1 is brought down, disconnecting the DUT from it
25 3) Another AP ("AP 2") is brought up, and DUT connects to it
26 4) DUT suspends while connected to AP 2
27 5) AP 2 is brought down, disconnecting the DUT from it while suspended
29 7) The DUT is woken from suspend
30 8) Verify that the DUT is connected to AP 1 upon resuming from suspend
32 We verify the connectivity status of the DUT on resume by parsing shill logs,
[all …]
|
| D | control.DisconnectBeforeSuspendDiffAP | 13 This test verifies that the DUT that suspends disconnected successfully
16 one that the DUT was last connected to before suspend.
20 1) AP ("AP 1") is brought up, and DUT connects to it
21 2) AP 1 is brought down, disconnecting the DUT from it
22 3) Another AP ("AP 2") is brought up, and DUT connects to it
23 4) AP 2 is brought down, disconnecting the DUT from it
24 5) DUT suspends while disconnected
26 7) The DUT is woken from suspend
27 8) Verify that the DUT is connected to AP 1 upon resuming from suspend
29 We verify the connectivity status of the DUT on resume by parsing shill logs,
[all …]
|
| D | control.Stress | 13 This test verifies that the DUT successfully reconnects to a network in dark
19 1) AP ("AP 1") is brought up, and DUT connects to it
20 2) AP 1 is brought down, disconnecting the DUT from it
21 3) Another AP ("AP 2") is brought up, and DUT connects to it
22 4) DUT suspends while connected to AP 2
23 5) AP 2 is brought down, disconnecting the DUT from it while suspended
26 8) The DUT is woken from suspend
27 9) Verify that the DUT is connected to AP 2 upon resuming from suspend
29 We verify the connectivity status of the DUT on resume by parsing shill logs,
30 since the delays involved in waking a DUT from suspend using autotest framework
[all …]
|
| /external/autotest/client/site_tests/suite_HWQual/ |
| D | README.txt | 16 - DUT: device under test
25 server requires Python, Wireless access to the DUT and basic Linux
46 - Install the Chrome OS test image on the DUT. The USB test image is
65 - Plug the USB device into the DUT and boot from it.
68 Install Chrome OS on the DUT:
73 - Cold boot the DUT -- turn the DUT off and then back on. This ensures
79 - Connect the DUT to the network and note its IP address <DUT_IP>. The
85 - Add the DUT root private key to ssh-agent on the Autotest server:
95 DUT.
98 - Make sure you can ssh as root to the DUT from the Autotest
[all …]
|
| /external/autotest/server/site_tests/system_ColdBoot/ |
| D | control | 9 PURPOSE = "Shut down DUT, then initiate a cold boot."
20 - remote shutdown of DUT via Linux commands (ssh)
21 - wait for DUT to stop responding to pings
23 - wait for DUT to start responding to pings
24 - attempt to log into DUT
|
| /external/toolchain-utils/binary_search_tool/sysroot_wrapper/ |
| D | glibc_test_script.sh | 19 DUT=172.17.186.180
31 cros flash ${DUT} latest &> /tmp/tmp_cros_flash_result.log
41 scp ${SSH_OPTS} /tmp/repro.sh root@${DUT}:/tmp
44 ( ssh ${SSH_OPTS} root@${DUT} -- /bin/bash -l /tmp/repro.sh ) > /tmp/result
|
| /external/autotest/server/site_tests/firmware_PDResetSoft/ |
| D | control | 18 - Ability of DUT to initate soft resets
19 - Ability of DUT to receive soft reset requests from Plankton
20 - If DUT is dualrole capable, soft resets are done with the DUT
|
| /external/autotest/server/site_tests/firmware_PDResetHard/ |
| D | control | 18 - Ability of DUT to initate hard resets
19 - Ability of DUT to receive hard resets
20 - If DUT is dualrole capable, hard resets are done with the DUT
|
| /external/autotest/client/site_tests/network_WiMaxPresent/ |
| D | control | 11 1. The DUT does not have a WiMAX module.
13 the DUT.
14 3. The WiMAX firmware is not installed on the DUT.
16 DUT.
29 on a DUT with a supported WiMAX module, but does not require a WiMAX network.
|
| /external/autotest/server/site_tests/network_WiFi_FastReconnectInDarkResume/ |
| D | control | 13 This test verifies that, during suspend, when a DUT is momentarily disconnected
14 from an AP that is still up, the DUT will reconnect to that AP during the same
17 We verify the connectivity status of the DUT on resume by parsing shill logs,
18 since the delays involved in waking a DUT from suspend using autotest framework
|
| /external/autotest/server/site_tests/firmware_PDDataSwap/ |
| D | control | 18 - If the DUT advertises support for data role swaps
19 - Tests if the DUT can receive data swap requests
20 - Tests if the DUT can initate data swap requests
|
| /external/autotest/server/site_tests/bluetooth_AdapterSuspendResume/ |
| D | control | 11 PURPOSE = 'Test bluetooth adapter state with suspending and resuming DUT.'
21 This test case verifies that the Bluetooth adapter of the DUT can
22 behave normally when subjected to suspending and resuming the DUT.
|
| D | control.stress_100 | 11 PURPOSE = 'Test bluetooth adapter state with suspending and resuming DUT.'
21 This test case verifies that the Bluetooth adapter of the DUT can
22 behave normally when subjected to suspending and resuming the DUT.
|
| /external/autotest/server/site_tests/firmware_PDPowerSwap/ |
| D | control | 18 - If the DUT advertises support for dualrole operation
19 - Tests if the DUT can receive power swap requests
20 - Tests if the DUT can initiate power swap requests
|
| /external/autotest/server/site_tests/cellular_StaleModemReboot/ |
| D | control | 25 command on the DUT and strips the state from its output. The test saves the
26 original modem state and reboots the DUT regardless of what state the modem
29 it tries to reboot the DUT for a maximum of two tries by default. User can
32 REBOOT STATES (If modem is in any of these states, DUT is cold rebooted using
46 first try, DUT will be rebooted.):
|
| /external/autotest/server/site_tests/display_EdidStress/ |
| D | control | 9 PURPOSE = "Stress DUT by switching EDID from among a large pool of EDIDs."
10 CRITERIA = "This test will fail if DUT does not see the emulated monitor."
20 DUT recognizes the emulated monitor and emits the correct video signal to
|
| D | control.weekly | 9 PURPOSE = "Stress DUT by switching EDID from among a large pool of EDIDs."
10 CRITERIA = "This test will fail if DUT does not see the emulated monitor."
23 DUT recognizes the emulated monitor and emits the correct video signal to
|
| /external/autotest/server/site_tests/provision_FactoryImage/ |
| D | control | 18 This test installs a specified factory image onto a servo-connected DUT.
30 is not specified and the DUT is in .cros, we will construct the right name
31 for its servo, and if the DUT isn't in .cros we will attempt to use localhost
42 'invoking test_that. Make sure the DUT you are '
|
| /external/autotest/client/site_tests/hardware_StorageWearoutDetect/ |
| D | control | 11 # This test measures the hardware health of individual DUTs. If it fails the DUT
13 # flakes due to random machine allocation when a DUT nears end of life (and slow
14 # bug filing/DUT replacement in lab).
|
| /external/autotest/server/site_tests/firmware_ECLidShutdown/ |
| D | control | 9 PURPOSE = "Verify functionality of DUT with GBB_FLAG_DISABLE_LID_SHUTDOWN"
21 - Verifies that closing lid in recovery will shutdown DUT
23 - Verifies that closing lid in recovery will not shutdown DUT
|
| /external/autotest/server/site_tests/sonic_AppTest/ |
| D | control | 27 sonic device. Note that the sonic host and the DUT need to be on the same
30 Usage: test_that <ip of Cros DUT> --board=<boardname of DUT>
|
| /external/autotest/server/site_tests/network_WiFi_LinkMonitorFailure/ |
| D | control | 13 This test checks how fast the DUT detects the link failure when an AP changes
14 its DHCP configuration, and how fast the DUT reconnects after the failure.
|