/usr/share/2013.com.canonical.certification:checkbox/jobs/suspend.txt.in is in plainbox-provider-checkbox 0.4-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | plugin: shell
id: suspend/network_before_suspend
depends: ethernet/detect
estimated_duration: 1.2
_description: Record the current network before suspending.
command: set -o pipefail; gateway_ping_test | tee $PLAINBOX_SESSION_SHARE/network_before_suspend.txt
plugin: shell
id: suspend/resolution_before_suspend
estimated_duration: 1.2
_description: Record the current resolution before suspending.
command: xrandr -q |grep '*'| awk '{print $1}' > $PLAINBOX_SESSION_SHARE/resolution_before_suspend.txt
plugin: shell
id: suspend/audio_before_suspend
estimated_duration: 1.0
requires:
device.category == 'AUDIO'
package.name == 'alsa-base'
_description: Record mixer settings before suspending.
command: audio_settings store --file=$PLAINBOX_SESSION_SHARE/audio_settings_before_suspend
plugin: shell
id: suspend/cpu_before_suspend
estimated_duration: 1.2
_description: Verify that all the CPUs are online before suspending
command: cpuinfo_resource > $PLAINBOX_SESSION_SHARE/cpuinfo_before_suspend
plugin: shell
id: suspend/memory_before_suspend
estimated_duration: 1.2
_description:
Dumps memory info to a file for comparison after suspend test has been run
command: meminfo_resource > $PLAINBOX_SESSION_SHARE/meminfo_before_suspend
plugin: shell
id: suspend/wireless_before_suspend
depends: wireless/wireless_connection
requires: device.category == 'WIRELESS'
command: nmcli -t -f UUID con status > $PLAINBOX_SESSION_SHARE/connections && connect_wireless && gateway_ping_test --interface=`nmcli dev list | grep -B 1 wireless | grep GENERAL.DEVICE | awk '{print $2}'` && for con in `cat $PLAINBOX_SESSION_SHARE/connections`; do nmcli con up uuid "$con"; done
estimated_duration: 20.0
_description:
This test disconnects all connections and then connects to the wireless
interface. It then checks the connection to confirm it's working as expected.
plugin: local
id: suspend/iperf_before_suspend_ether_auto
requires:
device.category == 'NETWORK'
command:
cat <<'EOF' | run_templates -s 'udev_resource | filter_templates -w "category=NETWORK" | awk "/path: / { print \$2 }" | xargs -n 1 sh -c "for i in \`ls /sys\$0/net 2>/dev/null\`; do echo \$0 \$i; done"'
plugin: shell
id: suspend/iperf_before_suspend_ether_auto_$2
depends: ethernet/detect
estimated_duration: 20.0
requires: device.path == "$1"
user: root
command: network -i $2 -t iperf
_description:
This test executes iperf connection performance/stability against all the ethernet devices found on the system before suspend.
EOF
_description:
This is an automated test to gather some info on the current state of your network devices. If no devices are found, the test will exit with an error.
plugin: local
id: suspend/iperf_before_suspend_wifi_auto
requires:
device.category == 'WIRELESS'
command:
cat <<'EOF' | run_templates -s 'udev_resource | filter_templates -w "category=WIRELESS" | awk "/path: / { print \$2 }" | xargs -n 1 sh -c "for i in \`ls /sys\$0/net 2>/dev/null\`; do echo \$0 \$i; done"'
plugin: shell
id: suspend/iperf_before_suspend_wifi_auto_$2
depends: wireless/wireless_connection
estimated_duration: 20.0
requires: device.path == "$1"
user: root
command: network -i $2 -t iperf
_description:
This test executes iperf connection performance/stability against all the ethernet devices found on the system before suspend.
EOF
_description:
This is an automated test to gather some info on the current state of your network devices. If no devices are found, the test will exit with an error.
plugin: shell
id: suspend/bluetooth_obex_before_suspend
estimated_duration: 10.0
requires:
package.name == 'bluez'
package.name == 'obexd-client'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill shows BT is soft blocked, removing before testing."
rfkill unblock bluetooth
sleep 3
fi
obex_send $BTDEVADDR $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg
_description:
This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_send_before_suspend
estimated_duration: 10.0
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR send 2>&1 | ansi_parser
_description:
This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_browse_before_suspend
estimated_duration: 10.0
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR browse 2>&1 | ansi_parser
_description:
This is an automated Bluetooth test. It emulates browsing on a remote device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_get_before_suspend
estimated_duration: 20.0
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR get 2>&1 | ansi_parser
_description:
This is an automated Bluetooth test. It receives the given file from a remote host specified by the BTDEVADDR environment variable
plugin: user-interact-verify
id: suspend/bluetooth_obex_before_suspend_manual
estimated_duration: 120.0
requires:
package.name == 'bluez'
package.name == 'obexd-client'
device.category == 'BLUETOOTH'
command: rfkill unblock bluetooth; obex_send `bluetooth_scan` $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg
_description:
PURPOSE:
This test will send the image 'JPEG_Color_Image_Ubuntu.jpg' to a specified device
STEPS:
1. Make sure Bluetooth is enabled by checking the Bluetooth indicator applet
2. Click "Test" and you will be prompted to enter the Bluetooth device name of a device that can accept file transfers (It may take a few moments after entering the name for the file to begin sending)
3. Accept any prompts that appear on both devices
VERIFICATION:
Was the data correctly transferred?
plugin: user-verify
id: suspend/suspend_advanced
requires:
sleep.mem == 'supported'
rtc.state == 'supported'
user: root
environ: PLAINBOX_SESSION_SHARE
command:
if type -P fwts >/dev/null; then
echo "Calling fwts"
set -o pipefail; fwts_test -f none -l $PLAINBOX_SESSION_SHARE/suspend_single -s s3 --s3-sleep-delay=30 --s3-device-check --s3-device-check-delay=45 | tee $PLAINBOX_SESSION_SHARE/suspend_single_times.log
else
echo "Calling sleep_test"
set -o pipefail; sleep_test -p | tee $PLAINBOX_SESSION_SHARE/suspend_single_times.log
fi
estimated_duration: 90.0
_description:
PURPOSE:
This test will check suspend and resume
STEPS:
1. Click "Test" and your system will suspend for about 30 - 60 seconds
2. Observe the Power LED to see if it blinks or changes color during suspend
3. If your system does not wake itself up after 60 seconds, please press the power button momentarily to wake the system manually
4. If your system fails to wake at all and must be rebooted, restart System Testing after reboot and mark this test as Failed
VERIFICATION:
Did your system suspend and resume correctly?
(NOTE: Please only consider whether the system successfully suspended and resumed. Power/Suspend LED verification will occur after this test is completed.)
plugin: shell
id: suspend/suspend_advanced_auto
requires:
sleep.mem == 'supported'
rtc.state == 'supported'
_description:
This is the automated version of suspend/suspend_advanced.
user: root
environ: PLAINBOX_SESSION_SHARE
command: set -o pipefail; fwts_test -f none -l $PLAINBOX_SESSION_SHARE/suspend_single -s s3 --s3-sleep-delay=30 --s3-device-check --s3-device-check-delay=45 | tee $PLAINBOX_SESSION_SHARE/suspend_single_times.log
estimated_duration: 90.000
plugin: shell
id: suspend/suspend-single-log-check
estimated_duration: 1.2
command: [ -e $PLAINBOX_SESSION_SHARE/suspend_single.log ] && sleep_test_log_check -v s3 $PLAINBOX_SESSION_SHARE/suspend_single.log
_description:
Automated check of the suspend log to look for errors reported by fwts
plugin: attachment
id: suspend/suspend-single-log-attach
command: [ -e $PLAINBOX_SESSION_SHARE/suspend_single.log ] && cat $PLAINBOX_SESSION_SHARE/suspend_single.log
_description:
Attaches the log from the single suspend/resume test to the results
plugin: shell
id: suspend/suspend-time-check
estimated_duration: 1.2
command: [ -e $PLAINBOX_SESSION_SHARE/suspend_single_times.log ] && sleep_time_check $PLAINBOX_SESSION_SHARE/suspend_single_times.log
_description:
Checks the sleep times to ensure that a machine suspends and resumes within a given threshold
plugin: user-interact-verify
id: power-management/usb_wakeup_keyboard
user: root
depends: suspend/suspend_advanced
estimated_duration: 120.0
command: pm-suspend
_description:
PURPOSE:
Wake up by USB keyboard
STEPS:
1. Enable "Wake by USB KB/Mouse" item in BIOS
2. Press "Test" to enter suspend (S3) mode
3. Press any key of USB keyboard to wake system up
VERIFICATION:
Did the system wake up from suspend mode when you pressed a keyboard key?
plugin: user-interact-verify
id: power-management/usb_wakeup_mouse
user: root
depends: suspend/suspend_advanced
estimated_duration: 120.0
command: pm-suspend
_description:
PURPOSE:
Wake up by USB mouse
STEPS:
1. Enable "Wake by USB KB/Mouse" item in BIOS
2. Press "Test" to enter suspend (S3) mode
3. Press any button of USB mouse to wake system up
VERIFICATION:
Did the system wake up from suspend mode when you pressed the mouse button?
plugin: shell
id: suspend/network_after_suspend
estimated_duration: 20.0
depends: suspend/suspend_advanced suspend/network_before_suspend
_description: Test the network after resuming.
command: network_wait; gateway_ping_test | diff $PLAINBOX_SESSION_SHARE/network_before_suspend.txt -
plugin: shell
id: suspend/resolution_after_suspend
depends: suspend/suspend_advanced suspend/resolution_before_suspend
estimated_duration: 1.2
_description: Test to see that we have the same resolution after resuming as before.
command: xrandr -q |grep '*'| awk '{print $1}' | diff $PLAINBOX_SESSION_SHARE/resolution_before_suspend.txt -
plugin: shell
id: suspend/audio_after_suspend
estimated_duration: 1.0
requires:
device.category == 'AUDIO'
package.name == 'alsa-base'
depends: suspend/suspend_advanced suspend/audio_before_suspend
_description: Verify that mixer settings after suspend are the same as before suspend.
command:
audio_settings store --file=$PLAINBOX_SESSION_SHARE/audio_settings_after_suspend; diff $PLAINBOX_SESSION_SHARE/audio_settings_before_suspend $PLAINBOX_SESSION_SHARE/audio_settings_after_suspend
plugin: shell
id: suspend/audio_after_suspend_auto
estimated_duration: 1.2
requires:
device.category == 'AUDIO'
package.name == 'alsa-base'
depends: suspend/suspend_advanced_auto suspend/audio_before_suspend
_description: Verify that mixer settings after suspend are the same as before suspend.
command:
audio_settings store --file=$PLAINBOX_SESSION_SHARE/audio_settings_after_suspend; diff $PLAINBOX_SESSION_SHARE/audio_settings_before_suspend $PLAINBOX_SESSION_SHARE/audio_settings_after_suspend
plugin: shell
id: suspend/cpu_after_suspend
estimated_duration: 1.2
depends: suspend/suspend_advanced suspend/cpu_before_suspend
_description: Verify that all CPUs are online after resuming.
command: cpuinfo_resource | diff $PLAINBOX_SESSION_SHARE/cpuinfo_before_suspend -
plugin: shell
id: suspend/cpu_after_suspend_auto
estimated_duration: 1.2
depends: suspend/suspend_advanced_auto suspend/cpu_before_suspend
_description: Verify that all CPUs are online after resuming.
command: cpuinfo_resource | diff $PLAINBOX_SESSION_SHARE/cpuinfo_before_suspend -
plugin: shell
id: suspend/memory_after_suspend
estimated_duration: 1.2
depends: suspend/suspend_advanced suspend/memory_before_suspend
_description:
Verify that all memory is available after resuming from suspend.
command: meminfo_resource | diff $PLAINBOX_SESSION_SHARE/meminfo_before_suspend -
plugin: shell
id: suspend/memory_after_suspend_auto
estimated_duration: 1.2
depends: suspend/suspend_advanced_auto suspend/memory_before_suspend
_description:
Verify that all memory is available after resuming from suspend.
command: meminfo_resource | diff $PLAINBOX_SESSION_SHARE/meminfo_before_suspend -
plugin: manual
id: suspend/display_after_suspend
estimated_duration: 120.0
depends: suspend/suspend_advanced
_description:
PURPOSE:
This test will check that the display is correct after suspend and resume
STEPS:
1. Check that your display does not show up visual artifacts after resuming.
VERIFICATION:
Does the display work normally after resuming from suspend?
plugin: shell
id: suspend/wireless_after_suspend
depends: suspend/suspend_advanced suspend/wireless_before_suspend
requires:
device.category == 'WIRELESS'
command: connect_wireless && gateway_ping_test --interface=`nmcli dev list | grep -B 1 wireless | grep GENERAL.DEVICE | awk '{print $2}'` && for con in `cat $PLAINBOX_SESSION_SHARE/connections`; do nmcli con up uuid "$con"; done
estimated_duration: 20.0
_description:
This test checks that the wireless interface is working after suspending the system. It
disconnects all interfaces and then connects to the wireless interface and checks that the
connection is working as expected.
plugin: shell
id: suspend/wireless_connection_after_suspend_wpa_bg
depends: suspend/suspend_advanced
estimated_duration: 20.0
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
user: root
environ: WPA_BG_SSID WPA_BG_PSK
command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_BG_SSID" EXIT; create_connection wifi $WPA_BG_SSID --security=wpa --key=$WPA_BG_PSK; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11b/g protocols after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_open_bg
depends: suspend/suspend_advanced
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
user: root
environ: OPEN_BG_SSID
command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_BG_SSID" EXIT; create_connection wifi $OPEN_BG_SSID; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using no
security and the 802.11b/g protocols after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_wpa_n
depends: suspend/suspend_advanced
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
IEEE_80211.n == 'supported'
user: root
environ: WPA_N_SSID WPA_N_PSK
command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_N_SSID" EXIT; create_connection wifi $WPA_N_SSID --security=wpa --key=$WPA_N_PSK; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11n protocol after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_open_n
depends: suspend/suspend_advanced
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
IEEE_80211.n == 'supported'
user: root
environ: OPEN_N_SSID
command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_N_SSID" EXIT; create_connection wifi $OPEN_N_SSID; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using no
security and the 802.11n protocol after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_wpa_ac
depends: suspend/suspend_advanced
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
IEEE_80211.ac == 'supported'
user: root
environ: WPA_AC_SSID WPA_AC_PSK
command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_AC_SSID" EXIT; create_connection wifi $WPA_AC_SSID --security=wpa --key=$WPA_AC_PSK; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11ac protocol after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_open_ac
depends: suspend/suspend_advanced
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
IEEE_80211.ac == 'supported'
user: root
environ: OPEN_AC_SSID
command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_AC_SSID" EXIT; create_connection wifi $OPEN_AC_SSID; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using no
security and the 802.11ac protocol after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_wpa_bg_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
user: root
environ: WPA_BG_SSID WPA_BG_PSK
command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_BG_SSID" EXIT; create_connection wifi $WPA_BG_SSID --security=wpa --key=$WPA_BG_PSK; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11b/g protocols after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_open_bg_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
user: root
environ: OPEN_BG_SSID
command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_BG_SSID" EXIT; create_connection wifi $OPEN_BG_SSID; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using no
security and the 802.11b/g protocols after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_wpa_n_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
user: root
environ: WPA_N_SSID WPA_N_PSK
command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_N_SSID" EXIT; create_connection wifi $WPA_N_SSID --security=wpa --key=$WPA_N_PSK; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11n protocol after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_open_n_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
user: root
environ: OPEN_N_SSID
command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_N_SSID" EXIT; create_connection wifi $OPEN_N_SSID; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using no
security and the 802.11n protocol after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_wpa_ac_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
user: root
environ: WPA_AC_SSID WPA_AC_PSK
command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_AC_SSID" EXIT; create_connection wifi $WPA_AC_SSID --security=wpa --key=$WPA_AC_PSK; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11ac protocol after the system has been suspended.
plugin: shell
id: suspend/wireless_connection_after_suspend_open_ac_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 1.2
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'multiple'
user: root
environ: OPEN_AC_SSID
command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_AC_SSID" EXIT; create_connection wifi $OPEN_AC_SSID; gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
Tests that the systems wireless hardware can connect to a router using no
security and the 802.11ac protocol after the system has been suspended.
plugin: local
id: suspend/iperf_after_suspend_ether_auto
estimated_duration: 30.0
requires:
device.category == 'NETWORK'
command:
cat <<'EOF' | run_templates -s 'udev_resource | filter_templates -w "category=NETWORK" | awk "/path: / { print \$2 }" | xargs -n 1 sh -c "for i in \`ls /sys\$0/net 2>/dev/null\`; do echo \$0 \$i; done"'
plugin: shell
id: suspend/iperf_after_suspend_ether_auto_$2
depends: suspend/suspend_advanced
requires: device.path == "$1"
user: root
command: network -i $2 -t iperf
_description:
This test executes iperf connection performance/stability against all the ethernet devices found on the system before suspend.
EOF
_description:
This is an automated test to gather some info on the current state of your network devices. If no devices are found, the test will exit with an error.
plugin: local
id: suspend/iperf_after_suspend_wifi_auto
estimated_duration: 30.0
requires:
device.category == 'WIRELESS'
command:
cat <<'EOF' | run_templates -s 'udev_resource | filter_templates -w "category=WIRELESS" | awk "/path: / { print \$2 }" | xargs -n 1 sh -c "for i in \`ls /sys\$0/net 2>/dev/null\`; do echo \$0 \$i; done"'
plugin: shell
id: suspend/iperf_before_suspend_wifi_auto_$2
depends: suspend/suspend_advanced
requires: device.path == "$1"
user: root
command: network -i $2 -t iperf
_description:
This test executes iperf connection performance/stability against all the ethernet devices found on the system before suspend.
EOF
_description:
This is an automated test to gather some info on the current state of your network devices. If no devices are found, the test will exit with an error.
plugin: user-interact-verify
id: suspend/wireless_connection_after_suspend_wpa_bg_manual
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'single'
user: root
environ: ROUTER_SSID ROUTER_PSK
command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID --security=wpa --key=$ROUTER_PSK && gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
PURPOSE:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11b/g protocols.
STEPS:
1. Open your routers configuration tool
2. Change the settings to only accept connections on the B and G wireless bands
3. Make sure the SSID is set to ROUTER_SSID
4. Change the security settings to use WPA2 and ensure the PSK matches that set in ROUTER_PSK
5. Click the 'Test' button to create a connection to the router and test the connection
VERIFICATION:
Verification is automated, do not change the automatically selected result.
plugin: user-interact-verify
id: suspend/wireless_connection_after_suspend_open_bg_manual
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'single'
user: root
environ: ROUTER_SSID
command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID && gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
PURPOSE:
Tests that the systems wireless hardware can connect to a router using
no security and the 802.11b/g protocols.
STEPS:
1. Open your routers configuration tool
2. Change the settings to only accept connections on the B and G wireless bands
3. Make sure the SSID is set to ROUTER_SSID
4. Change the security settings to use no security
5. Click the 'Test' button to create a connection to the router and test the connection
VERIFICATION:
Verification is automated, do not change the automatically selected result.
plugin: user-interact-verify
id: suspend/wireless_connection_after_suspend_wpa_n_manual
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'single'
user: root
environ: ROUTER_SSID ROUTER_PSK
command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID --security=wpa --key=$ROUTER_PSK && gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
PURPOSE:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11n protocols.
STEPS:
1. Open your routers configuration tool
2. Change the settings to only accept connections on the N wireless band
3. Make sure the SSID is set to ROUTER_SSID
4. Change the security settings to use WPA2 and ensure the PSK matches that set in ROUTER_PSK
5. Click the 'Test' button to create a connection to the router and test the connection
VERIFICATION:
Verification is automated, do not change the automatically selected result.
plugin: user-interact-verify
id: suspend/wireless_connection_after_suspend_open_n_manual
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'single'
user: root
environ: ROUTER_SSID
command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID && gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
PURPOSE:
Tests that the systems wireless hardware can connect to a router using
no security and the 802.11n protocol.
STEPS:
1. Open your routers configuration tool
2. Change the settings to only accept connections on the N wireless band
3. Make sure the SSID is set to ROUTER_SSID
4. Change the security settings to use no security
5. Click the 'Test' button to create a connection to the router and test the connection
VERIFICATION:
Verification is automated, do not change the automatically selected result.
plugin: user-interact-verify
id: suspend/wireless_connection_after_suspend_wpa_ac_manual
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'single'
user: root
environ: ROUTER_SSID ROUTER_PSK
command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID --security=wpa --key=$ROUTER_PSK && gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
PURPOSE:
Tests that the systems wireless hardware can connect to a router using WPA
security and the 802.11ac protocol.
STEPS:
1. Open your routers configuration tool
2. Change the settings to only accept connections on the 802.11ac protocol.
3. Make sure the SSID is set to ROUTER_SSID
4. Change the security settings to use WPA2 and ensure the PSK matches that set in ROUTER_PSK
5. Click the 'Test' button to create a connection to the router and test the connection
VERIFICATION:
Verification is automated, do not change the automatically selected result.
plugin: user-interact-verify
id: suspend/wireless_connection_after_suspend_open_ac_manual
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'WIRELESS'
environment.ROUTERS == 'single'
user: root
environ: ROUTER_SSID
command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID && gateway_ping_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
_description:
PURPOSE:
Tests that the systems wireless hardware can connect to a router using
no security and the 802.11ac protocol.
STEPS:
1. Open your routers configuration tool
2. Change the settings to only accept connections on the 802.11ac protocol.
3. Make sure the SSID is set to ROUTER_SSID
4. Change the security settings to use no security
5. Click the 'Test' button to create a connection to the router and test the connection
VERIFICATION:
Verification is automated, do not change the automatically selected result.
plugin: shell
id: suspend/bluetooth_detect_after_suspend
depends: suspend/suspend_advanced bluetooth/detect-output
estimated_duration: 1.2
requires:
package.name == 'bluez'
device.category == 'BLUETOOTH'
command:
if rfkill list bluetooth | grep -q 'Hard blocked: yes'; then
echo "rfkill shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'; then
echo "rfkill shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
output=$(hcitool dev | tail -n+2 | awk '{print $2}')
echo $output | diff $PLAINBOX_SESSION_SHARE/bluetooth_address -
if [ -z "$output" ]; then
echo "BT hardware not available"
exit 1
fi
_description:
This test grabs the hardware address of the bluetooth adapter after suspend and compares it to the address grabbed before suspend.
plugin: shell
id: suspend/bluetooth_obex_after_suspend
depends: suspend/suspend_advanced suspend/bluetooth_obex_before_suspend
estimated_duration: 10.0
requires:
package.name == 'bluez'
package.name == 'obexd-client'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill shows BT is soft blocked, removing before testing."
rfkill unblock bluetooth
sleep 3
fi
obex_send $BTDEVADDR $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg
_description:
This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_after_suspend_auto
depends: suspend/suspend_advanced_auto suspend/bluetooth_obex_before_suspend
estimated_duration: 10.0
requires:
package.name == 'bluez'
package.name == 'obexd-client'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill shows BT is soft blocked, removing before testing."
rfkill unblock bluetooth
sleep 3
fi
obex_send $BTDEVADDR $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg
_description:
This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_send_after_suspend
depends: suspend/suspend_advanced
estimated_duration: 10.0
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR send 2>&1 | ansi_parser
_description:
This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_send_after_suspend_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 10.0
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR send 2>&1 | ansi_parser
_description:
This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_browse_after_suspend
depends: suspend/suspend_advanced
estimated_duration: 10.0
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR browse 2>&1 | ansi_parser
_description:
This is an automated Bluetooth test. It emulates browsing on a remote device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_browse_after_suspend_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 20.0
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR browse 2>&1 | ansi_parser
_description:
This is an automated Bluetooth test. It emulates browsing on a remote device specified by the BTDEVADDR environment variable.
plugin: shell
id: suspend/bluetooth_obex_get_after_suspend
estimated_duration: 20.0
depends: suspend/suspend_advanced
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR get 2>&1 | ansi_parser
_description:
This is an automated Bluetooth test. It receives the given file from a remote host specified by the BTDEVADDR environment variable
plugin: shell
id: suspend/bluetooth_obex_get_after_suspend_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 20.0
requires:
package.name == 'bluez'
package.name == 'obexftp'
device.category == 'BLUETOOTH'
command:
if [ -z "$BTDEVADDR" ]
then
echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
exit 1
fi
if rfkill list bluetooth | grep -q 'Hard blocked: yes'
then
echo "rfkill list shows BT is hard blocked"
fi
if rfkill list bluetooth | grep -q 'Soft blocked: yes'
then
echo "rfkill list shows BT is soft blocked, removing before testing"
rfkill unblock bluetooth
sleep 3
fi
set -o pipefail; bluetooth_test $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR get 2>&1 | ansi_parser
_description:
This is an automated Bluetooth test. It receives the given file from a remote host specified by the BTDEVADDR environment variable
plugin: user-interact-verify
id: suspend/bluetooth_obex_after_suspend_manual
depends: suspend/suspend_advanced suspend/bluetooth_obex_before_suspend_manual
estimated_duration: 120.0
requires:
package.name == 'bluez'
package.name == 'obexd-client'
device.category == 'BLUETOOTH'
command: rfkill unblock bluetooth; obex_send `bluetooth_scan` $PLAINBOX_PROVIDER_DATA/images/JPEG_Color_Image_Ubuntu.jpg
_description:
PURPOSE:
This test will send the image 'JPEG_Color_Image_Ubuntu.jpg' to a specified device
STEPS:
1. Click "Test" and you will be prompted to enter the Bluetooth device name of a device that can accept file transfers (It may take a few moments after entering the name for the file to begin sending)
2. Accept any prompts that appear on both devices
VERIFICATION:
Was the data correctly transferred?
plugin: user-interact-verify
id: suspend/cycle_resolutions_after_suspend
estimated_duration: 120.0
requires: package.name == 'xorg'
depends: suspend/suspend_advanced graphics/cycle_resolution
command: xrandr_cycle --keyword=after_suspend --screenshot-dir $PLAINBOX_SESSION_SHARE
_description:
PURPOSE:
This test will cycle through the detected display modes
STEPS:
1. Click "Test" and the display will cycle trough the display modes
VERIFICATION:
Did your display look fine in the detected mode?
plugin: shell
id: suspend/cycle_resolutions_after_suspend_auto
estimated_duration: 1.2
requires: package.name == 'xorg'
depends: suspend/suspend_advanced_auto graphics/cycle_resolution
_description:
This test will check to make sure supported video modes work after a suspend and resume.
This is done automatically by taking screenshots and uploading them as an attachment.
command: xrandr_cycle --keyword=after_suspend --screenshot-dir $PLAINBOX_SESSION_SHARE
plugin: attachment
id: suspend/xrandr_screens_after_suspend.tar.gz
depends: suspend/cycle_resolutions_after_suspend_auto
command: [ -e $PLAINBOX_SESSION_SHARE/xrandr_screens_after_suspend.tgz ] && cat $PLAINBOX_SESSION_SHARE/xrandr_screens_after_suspend.tgz
_description: This attaches screenshots from the suspend/cycle_resolutions_after_suspend_auto test to the results submission.
plugin: shell
id: suspend/record_playback_after_suspend
estimated_duration: 10.0
depends: suspend/suspend_advanced
requires:
package.name == 'python3-gi'
package.name == 'gir1.2-gstreamer-1.0'
package.name == 'libgstreamer1.0-0'
package.name == 'gstreamer1.0-plugins-good'
package.name == 'gstreamer1.0-pulseaudio'
package.name == 'alsa-base'
device.category == 'AUDIO'
command: audio_test
_description:
This will check to make sure that your audio device works properly after a suspend and resume. This may work fine with speakers and onboard microphone, however, it works best if used with a cable connecting the audio-out jack to the audio-in jack.
plugin: shell
id: suspend/record_playback_after_suspend_auto
estimated_duration: 10.0
depends: suspend/suspend_advanced_auto
requires:
package.name == 'python3-gi'
package.name == 'gir1.2-gstreamer-1.0'
package.name == 'libgstreamer1.0-0'
package.name == 'gstreamer1.0-plugins-good'
package.name == 'gstreamer1.0-pulseaudio'
package.name == 'alsa-base'
device.category == 'AUDIO'
command: audio_test
_description:
This will check to make sure that your audio device works properly after a suspend and resume. This may work fine with speakers and onboard microphone, however, it works best if used with a cable connecting the audio-out jack to the audio-in jack.
plugin: attachment
id: suspend/suspend-auto-single-log-attach
command: [ -e $PLAINBOX_SESSION_SHARE/suspend_auto_single_log ] && cat $PLAINBOX_SESSION_SHARE/suspend_auto_single_log
_description:
Attaches the log from the single suspend/resume test to the results
plugin: shell
id: suspend/screenshot_after_suspend
estimated_duration: 10.0
depends: suspend/suspend_advanced_auto
requires: package.name == 'fswebcam'
command: set -o pipefail; camera_test still --device=/dev/external_webcam -f ${PLAINBOX_SESSION_SHARE}/screenshot_after_suspend.jpg -q 2>&1 | ansi_parser
_description:
PURPOSE:
Take a screengrab of the current screen after suspend (logged on Unity desktop)
STEPS:
1. Take picture using USB webcam
VERIFICATION:
Review attachment manually later
plugin: attachment
id: screenshot_after_suspend.jpg
depends: suspend/screenshot_after_suspend
command: base64 ${PLAINBOX_SESSION_SHARE}/screenshot_after_suspend.jpg
_description: Attaches the screenshot captured in graphics/screenshot.
plugin: shell
id: suspend/gpu_lockup_after_suspend
estimated_duration: 10.0
requires:
package.name == 'wmctrl'
package.name == 'mesa-utils'
package.name == 'firefox'
depends: suspend/suspend_advanced_auto
command: gpu_test
_description:
PURPOSE:
Do some challenging operations then check for lockup on the GPU
STEPS:
1. Create 2 glxgears windows and move them quickly
2. Switch workspaces with wmctrl
3. Launch an HTML5 video playback in firefox
VERIFICATION:
After a 60s workload, check kern.log for reported GPU errors
plugin: shell
id: suspend/wifi_resume_time
depends: suspend/suspend_advanced
requires:
device.category == 'WIRELESS'
command: network_reconnect_resume_test -t 90 -d wifi
estimated_duration: 0.530
_description:
Checks the length of time it takes to reconnect an existing wifi connection
after a suspend/resume cycle.
plugin: shell
id: suspend/wifi_resume_time_auto
estimated_duration: 1.2
depends: suspend/suspend_advanced_auto
requires:
device.category == 'WIRELESS'
command: network_reconnect_resume_test -t 90 -d wifi
_description:
Checks the length of time it takes to reconnect an existing wifi connection
after a suspend/resume cycle.
plugin: shell
id: suspend/network_resume_time
depends: suspend/suspend_advanced
estimated_duration: 1.2
requires:
device.category == 'NETWORK'
command: network_reconnect_resume_test -t 10 -d wired
_description:
Checks the length of time it takes to reconnect an existing wired connection
after a suspend/resume cycle.
plugin: shell
id: suspend/network_resume_time_auto
depends: suspend/suspend_advanced_auto
estimated_duration: 1.2
requires:
device.category == 'NETWORK'
command: network_reconnect_resume_test -t 10 -d wired
_description:
Checks the length of time it takes to reconnect an existing wired connection
after a suspend/resume cycle.
plugin: manual
id: suspend/led_after_suspend/power
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
Validate that the power LED operated the same after resuming from suspend
STEPS:
1. Power LED should be on while device is switched on
VERIFICATION:
Does the power LED remain on after resuming from suspend?
plugin: manual
id: suspend/led_after_suspend/battery-charging
estimated_duration: 120.0
depends: suspend/suspend_advanced
_description:
PURPOSE:
Validate that the battery light shows charging status after resuming from suspend
STEPS:
1. Let system run on battery for a while
2. Plug in AC plug
VERIFICATION:
Did the battery indicator LED still turn orange after resuming from suspend?
plugin: manual
id: suspend/led_after_suspend/battery-charged
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
Validate that the battery LED properly displays charged status after resuming from suspend
STEPS:
1. Let system run on battery for a short time
2. Plug in AC
3. Let system run on AC
VERIFICATION:
Does the orange battery LED still shut off when system is fully charged after resuming from suspend?
plugin: manual
id: suspend/led_after_suspend/battery-low
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
Validate that the battery LED indicated low power after resuming from suspend
STEPS:
1. Let system run on battery for several hours
2. Monitor battery LED carefully
VERIFICATION:
Does the LED light orange when battery is low after resuming from suspend?
plugin: user-interact-verify
id: suspend/led_after_suspend/hdd
depends: suspend/suspend_advanced
estimated_duration: 120.0
command: led_hdd_test
_description:
PURPOSE:
Validate that the HDD LED still operates as expected after resuming from suspend
STEPS:
1. Select "Test" to write and read a temporary file for a few seconds
2. HDD LED should blink when writing to/reading from HDD
VERIFICATION:
Did the HDD LED still blink with HDD activity after resuming from suspend?
plugin: user-interact-verify
id: suspend/led_after_suspend/numeric-keypad
estimated_duration: 120.0
depends: suspend/suspend_advanced
command: keyboard_test
_description:
PURPOSE:
Validate that the numeric keypad LED operates the same before and after resuming from suspend
STEPS:
1. Press "Block Num" key to toggle numeric keypad LED
2. Click on the "Test" button to open a window to verify your typing
3. Type using the numeric keypad both when the LED is on and off
VERIFICATION:
1. Numeric keypad LED status should toggle everytime the "Block Num" key is pressed
2. Numbers should only be entered in the keyboard verification window when the LED is on
plugin: manual
id: suspend/led_after_suspend/caps-lock
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
Validate that the Caps Lock key operates the same before and after resuming from suspend
STEPS:
1. Press "Block Cap Keys" to activate/deactivate cap keys blocking
2. Cap Keys LED should be switched on/off every time the key is pressed
VERIFICATION:
Did the Cap Keys LED light as expected after resuming from suspend?
plugin: manual
id: suspend/led_after_suspend/wlan
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
WLAN LED verification after resuming from suspend
STEPS:
1. Make sure WLAN connection is established
2. WLAN LED should light
VERIFICATION:
Did the WLAN LED light as expected after resuming from suspend?
plugin: manual
id: suspend/led_after_suspend/wlan-disabled
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
Validate that WLAN LED shuts off when disabled after resuming from suspend
STEPS:
1. Connect to AP
2. Use Physical switch to disable WLAN
3. Re-enable
4. Use Network-Manager to disable WLAN
VERIFICATION:
Did the LED turn off then WLAN is disabled after resuming from suspend?
plugin: manual
id: suspend/led_after_suspend/bluetooth
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
Validate that the Bluetooth LED turns on and off when BT is enabled/disabled after resuming from suspend
STEPS:
1. Switch bluetooth off from a hardware switch (if present)
2. Switch bluetooth back on
3. Switch bluetooth off from the panel applet
4. Switch bluetooth back on
VERIFICATION:
Did the bluetooth LED turn off and on twice after resuming from suspend?
plugin: user-interact-verify
id: suspend/led_after_suspend/camera
estimated_duration: 120.0
depends:
camera/detect
suspend/suspend_advanced
command: camera_test led
_description:
PURPOSE:
Validate that the camera LED still works as expected after resuming from suspend
STEPS:
1. Select Test to activate camera
2. Camera LED should light for a few seconds
VERIFICATION:
Did the camera LED still turn on and off after resuming from suspend?
plugin: manual
id: suspend/led_after_suspend/touchpad
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
Touchpad LED verification after resuming from suspend
STEPS:
1. Click on the touchpad button or press key combination to enable/disable touchpad button
2. Slide your finger on the touchpad
VERIFICATION:
1. Touchpad LED status should toggle everytime the button is clicked or the key combination is pressed
2. When the LED is on, the mouse pointer should move on touchpad usage
3. When the LED is off, the mouse pointer should not move on touchpad usage
plugin: manual
id: suspend/led_after_suspend/wireless
depends: suspend/suspend_advanced
estimated_duration: 120.0
_description:
PURPOSE:
Validate Wireless (WLAN + Bluetooth) LED operated the same after resuming from suspend
STEPS:
1. Make sure WLAN connection is established and Bluetooth is enabled.
2. WLAN/Bluetooth LED should light
3. Switch WLAN and Bluetooth off from a hardware switch (if present)
4. Switch them back on
5. Switch WLAN and Bluetooth off from the panel applet
6. Switch them back on
VERIFICATION:
Did the WLAN/Bluetooth LED light as expected after resuming from suspend?
plugin: manual
id: suspend/keys_after_suspend/brightness
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires: dmi.product in ['Notebook','Laptop','Portable']
_description:
PURPOSE:
This test will test the brightness key after resuming from suspend
STEPS:
1. Press the brightness buttons on the keyboard
VERIFICATION:
Did the brightness change following to your key presses after resuming from suspend?
plugin: user-interact-verify
id: suspend/keys_after_suspend/volume
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'KEYBOARD'
user: root
command: key_test -s '0xe02e,0xe0ae:Volume Up' '0xe030,0xe0b0:Volume Down'
_description:
PURPOSE:
This test will test the volume keys of your keyboard after resuming from suspend
STEPS:
Skip this test if your computer has no volume keys.
1. Click test to open a window on which to test the volume keys.
2. If all the keys work, the test will be marked as passed.
VERIFICATION:
Did the volume change following to your key presses?
plugin: user-interact-verify
id: suspend/keys_after_suspend/mute
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'KEYBOARD'
user: root
command: key_test -s '0xe020,0xe0a0:Mute'
_description:
PURPOSE:
This test will test the mute key of your keyboard after resuming from suspend
STEPS:
1. Click test to open a window on which to test the mute key.
2. If the key works, the test will pass and the window will close.
VERIFICATION:
Did the volume mute following your key presses?
plugin: manual
id: suspend/keys_after_suspend/sleep
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'KEYBOARD'
_description:
PURPOSE:
This test will test the sleep key after resuming from suspend
STEPS:
1. Press the sleep key on the keyboard
2. Wake your system up by pressing the power button
VERIFICATION:
Did the system go to sleep after pressing the sleep key after resuming from suspend?
plugin: user-interact-verify
id: suspend/keys_after_suspend/battery-info
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires: dmi.product in ['Notebook','Laptop','Portable']
user: root
command: key_test -s '0xe071,0xef1:Battery Info'
_description:
PURPOSE:
This test will test the battery information key after resuming from suspend
STEPS:
Skip this test if you do not have a Battery Button.
1. Click Test to begin
2. Press the Battery Info button (or combo like Fn+F3)
3: Close the Power Statistics tool if it opens
VERIFICATION:
Did the Battery Info key work as expected after resuming from suspend?
plugin: manual
id: suspend/keys_after_suspend/wireless
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires: dmi.product in ['Notebook','Laptop','Portable']
_description:
PURPOSE:
This test will test the wireless key after resuming from suspend
STEPS:
1. Press the wireless key on the keyboard
2. Press the same key again
VERIFICATION:
Did the wireless go off on the first press and on again on the second after resuming from suspend?
plugin: user-interact-verify
id: suspend/keys_after_suspend/media-control
estimated_duration: 120.0
depends: suspend/suspend_advanced
requires:
device.category == 'KEYBOARD'
user: root
command: key_test -s 0xe010,0xe090:Previous 0xe024,0xe0a4:Stop 0xe019,0xe099:Next 0xe022,0xe0a2:Play
_description:
PURPOSE:
This test will test the media keys of your keyboard after resuming from suspend
STEPS:
Skip this test if your computer has no media keys.
1. Click test to open a window on which to test the media keys.
2. If all the keys work, the test will be marked as passed.
VERIFICATION:
Do the keys work as expected after resuming from suspend?
plugin: user-interact-verify
id: suspend/keys_after_suspend/super
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires:
device.category == 'KEYBOARD'
user: root
command: key_test -s '0xe05b,0xe0db:Left Super Key'
_description:
PURPOSE:
This test will test the super key of your keyboard after resuming from suspend
STEPS:
1. Click test to open a window on which to test the super key.
2. If the key works, the test will pass and the window will close.
VERIFICATION:
Does the super key work as expected after resuming from suspend?
plugin: manual
id: suspend/keys_after_suspend/video-out
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires: dmi.product in ['Notebook','Laptop','Portable']
_description:
PURPOSE:
Validate that the External Video hot key is working as expected after resuming from suspend
STEPS:
1. Plug in an external monitor
2. Press the display hot key to change the monitors configuration
VERIFICATION:
Check that the video signal can be mirrored, extended, displayed on external or onboard only, after resuming from suspend.
plugin: manual
id: suspend/keys_after_suspend/touchpad
depends: suspend/suspend_advanced
estimated_duration: 120.0
requires: dmi.product in ['Notebook','Laptop','Portable']
_description:
PURPOSE:
Verify touchpad hotkey toggles touchpad functionality on and off after resuming from suspend
STEPS:
1. Verify the touchpad is functional
2. Tap the touchpad toggle hotkey
3. Tap the touchpad toggle hotkey again
VERIFICATION:
Verify the touchpad has been disabled and re-enabled.
plugin: user-interact
id: suspend/usb_insert_after_suspend
estimated_duration: 30.0
depends:
suspend/suspend_advanced
command: removable_storage_watcher insert usb
_description:
PURPOSE:
This test will check that the system correctly detects the insertion of
a USB storage device after suspend and resume.
STEPS:
1. Click "Test" and insert a USB storage device (pen-drive/HDD).
(Note: this test will time-out after 20 seconds.)
2. Do not unplug the device after the test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: suspend/usb3_insert_after_suspend
estimated_duration: 30.0
requires:
usb.usb3 == 'supported'
depends:
suspend/suspend_advanced
command: removable_storage_watcher -m 500000000 insert usb
_description:
PURPOSE:
This test will check that the system correctly detects the insertion of
a USB 3.0 storage device after suspend and resume.
STEPS:
1. Click "Test" and insert a USB 3.0 storage device (pen-drive/HDD) in
a USB 3.0 port. (Note: this test will time-out after 20 seconds.)
2. Do not unplug the device after the test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: suspend/usb_remove_after_suspend
estimated_duration: 30.0
depends:
suspend/usb_insert_after_suspend
command: removable_storage_watcher remove usb
_description:
PURPOSE:
This test will check that the system correctly detects the removal of
a USB storage device after suspend.
STEPS:
1. Click "Test" and remove the USB device.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: suspend/usb3_remove_after_suspend
estimated_duration: 30.0
depends:
suspend/usb3_insert_after_suspend
requires:
usb.usb3 == 'supported'
command: removable_storage_watcher -m 500000000 remove usb
_description:
PURPOSE:
This test will check that the system correctly detects the removal of
a USB 3.0 storage device after suspend
STEPS:
1. Click "Test" and remove the USB 3.0 device.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: suspend/usb_storage_automated_after_suspend
estimated_duration: 1.2
depends: suspend/usb_insert_after_suspend
user: root
command: removable_storage_test -s 268400000 usb
_description:
This test is automated and executes after the suspend/usb_insert_after_suspend
test is run.
plugin: shell
id: suspend/usb3_storage_automated_after_suspend
estimated_duration: 1.2
requires:
usb.usb3 == 'supported'
depends: suspend/usb3_insert_after_suspend
user: root
command: removable_storage_test -s 268400000 -m 500000000 -p 7 usb
_description:
This test is automated and executes after the suspend/usb3_insert_after_suspend
test is run.
plugin: shell
id: suspend/usb_storage_preinserted_after_suspend
estimated_duration: 1.2
user: root
depends: suspend/suspend_advanced_auto
command: removable_storage_test -l usb && removable_storage_test -s 268400000 usb
_description:
This is an automated version of usb/storage-automated and assumes that the
server has usb storage devices plugged in prior to checkbox execution. It
is intended for servers and SRU automated testing.
plugin: shell
id: suspend/usb3_storage_preinserted_after_suspend
estimated_duration: 1.2
user: root
requires:
usb.usb3 == 'supported'
depends: suspend/suspend_advanced_auto
command: removable_storage_test -l usb && removable_storage_test -s 268400000 -m 500000000 -p 7 usb
_description:
This is an automated version of usb3/storage-automated and assumes that the
server has usb 3.0 storage devices plugged in prior to checkbox execution. It
is intended for servers and SRU automated testing.
plugin: shell
id: suspend/usb_performance_after_suspend
depends: suspend/usb_insert_after_suspend
user: root
estimated_duration: 45.00
command: removable_storage_test -s 268400000 -p 15 usb
_description:
This test will check that your USB 2.0 port transfers data at a
minimum expected speed.
plugin: shell
id: suspend/usb3_superspeed_performance_after_suspend
requires:
usb.usb3 == 'supported'
depends: suspend/usb3_insert_after_suspend
user: root
estimated_duration: 45.00
command: removable_storage_test -s 268400000 -m 500000000 -p 60 usb
_description:
This test will check that your USB 3.0 port transfers data at a
minimum expected speed in accordance with the specification of
USB 3.0 SuperSpeed mode.
plugin: user-interact
id: suspend/mmc-insert-after-suspend
estimated_duration: 30.0
depends: suspend/suspend_advanced
command: removable_storage_watcher --memorycard insert sdio usb scsi
_description:
PURPOSE:
This test will check that the systems media card reader can
detect the insertion of an MMC card after the system has been suspended
STEPS:
1. Click "Test" and insert an MMC card into the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
2. Do not remove the device after this test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: suspend/mmc-storage-after-suspend
depends: suspend/mmc-insert-after-suspend
estimated_duration: 10.0
user: root
command: removable_storage_test -s 67120000 --memorycard sdio usb scsi
_description:
This test is automated and executes after the mediacard/mmc-insert-after-suspend test
is run. It tests reading and writing to the MMC card after the system has been suspended.
plugin: user-interact
id: suspend/mmc-remove-after-suspend
depends: suspend/mmc-insert-after-suspend
estimated_duration: 30.0
command: removable_storage_watcher --memorycard remove sdio usb scsi
_description:
PURPOSE:
This test will check that the system correctly detects the removal
of an MMC card from the systems card reader after the system has been suspended.
STEPS:
1. Click "Test" and remove the MMC card from the reader.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: suspend/sd-insert-after-suspend
estimated_duration: 30.0
depends: suspend/suspend_advanced
command: removable_storage_watcher --memorycard insert sdio usb scsi
_description:
PURPOSE:
This test will check that the systems media card reader can
detect the insertion of an UNLOCKED SD card after the system
has been suspended
STEPS:
1. Click "Test" and insert an UNLOCKED SD card into the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
2. Do not remove the device after this test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: suspend/sd-storage-after-suspend
estimated_duration: 10.0
depends: suspend/sd-insert-after-suspend
user: root
command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
_description:
This test is automated and executes after the mediacard/sd-insert-after-suspend test
is run. It tests reading and writing to the SD card after the system has been suspended.
plugin: user-interact
id: suspend/sd-remove-after-suspend
estimated_duration: 30.0
depends: suspend/sd-insert-after-suspend
command: removable_storage_watcher --memorycard remove sdio usb scsi
_description:
PURPOSE:
This test will check that the system correctly detects
the removal of an SD card from the systems card reader
after the system has been suspended.
STEPS:
1. Click "Test" and remove the SD card from the reader.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: suspend/sdhc-insert-after-suspend
estimated_duration: 30.0
depends: suspend/suspend_advanced
command: removable_storage_watcher --memorycard insert sdio usb scsi
_description:
PURPOSE:
This test will check that the systems media card reader can
detect the insertion of an UNLOCKED SDHC media card after the
system has been suspended
STEPS:
1. Click "Test" and insert an UNLOCKED SDHC card into the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
2. Do not remove the device after this test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: suspend/sdhc-storage-after-suspend
estimated_duration: 10.0
depends: suspend/sdhc-insert-after-suspend
user: root
command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
_description:
This test is automated and executes after the mediacard/sdhc-insert-after-suspend test
is run. It tests reading and writing to the SDHC card after the system has been suspended.
plugin: user-interact
id: suspend/sdhc-remove-after-suspend
estimated_duration: 30.0
depends: suspend/sdhc-insert-after-suspend
command: removable_storage_watcher --memorycard remove sdio usb scsi
_description:
PURPOSE:
This test will check that the system correctly detects the removal
of an SDHC card from the systems card reader after the system has been suspended.
STEPS:
1. Click "Test" and remove the SDHC card from the reader.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: mediacard/cf-insert-after-suspend
estimated_duration: 30.0
depends: suspend/suspend_advanced
command: removable_storage_watcher --memorycard insert sdio usb scsi
_description:
PURPOSE:
This test will check that the systems media card reader can
detect the insertion of a CF card after the system has been suspended
STEPS:
1. Click "Test" and insert a CF card into the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
2. Do not remove the device after this test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: mediacard/cf-storage-after-suspend
estimated_duration: 10.0
depends: mediacard/cf-insert-after-suspend
user: root
command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
_description:
This test is automated and executes after the mediacard/cf-insert-after-suspend test
is run. It tests reading and writing to the CF card after the system has been suspended.
plugin: user-interact
id: mediacard/cf-remove-after-suspend
estimated_duration: 30.0
depends: mediacard/cf-insert-after-suspend
command: removable_storage_watcher --memorycard remove sdio usb scsi
_description:
PURPOSE:
This test will check that the system correctly detects the removal
of a CF card from the systems card reader after the system has been suspended.
STEPS:
1. Click "Test" and remove the CF card from the reader.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: mediacard/sdxc-insert-after-suspend
estimated_duration: 30.0
depends: suspend/suspend_advanced
command: removable_storage_watcher --memorycard insert sdio usb scsi
_description:
PURPOSE:
This test will check that the systems media card reader can
detect the insertion of a SDXC card after the system has been suspended
STEPS:
1. Click "Test" and insert a SDXC card into the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
2. Do not remove the device after this test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: mediacard/sdxc-storage-after-suspend
estimated_duration: 10.0
depends: mediacard/sdxc-insert-after-suspend
user: root
command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
_description:
This test is automated and executes after the mediacard/sdxc-insert-after-suspend test
is run. It tests reading and writing to the SDXC card after the system has been suspended.
plugin: user-interact
id: mediacard/sdxc-remove-after-suspend
depends: mediacard/sdxc-insert-after-suspend
estimated_duration: 30.0
command: removable_storage_watcher --memorycard remove sdio usb scsi
_description:
PURPOSE:
This test will check that the system correctly detects the removal
of a SDXC card from the systems card reader after the system has been suspended.
STEPS:
1. Click "Test" and remove the SDXC card from the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: mediacard/ms-insert-after-suspend
estimated_duration: 30.0
depends: suspend/suspend_advanced
command: removable_storage_watcher --memorycard insert sdio usb scsi
_description:
PURPOSE:
This test will check that the systems media card reader can
detect the insertion of a MS card after the system has been suspended
STEPS:
1. Click "Test" and insert a MS card into the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
2. Do not remove the device after this test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: mediacard/ms-storage-after-suspend
estimated_duration: 10.0
depends: mediacard/ms-insert-after-suspend
user: root
command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
_description:
This test is automated and executes after the mediacard/ms-insert-after-suspend test
is run. It tests reading and writing to the MS card after the system has been suspended.
plugin: user-interact
id: mediacard/ms-remove-after-suspend
estimated_duration: 30.0
depends: mediacard/ms-insert-after-suspend
command: removable_storage_watcher --memorycard remove sdio usb scsi
_description:
PURPOSE:
This test will check that the system correctly detects the removal
of a MS card from the systems card reader after the system has been suspended.
STEPS:
1. Click "Test" and remove the MS card from the reader.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: mediacard/msp-insert-after-suspend
estimated_duration: 30.0
depends: suspend/suspend_advanced
command: removable_storage_watcher --memorycard insert sdio usb scsi
_description:
PURPOSE:
This test will check that the systems media card reader can
detect the insertion of a MSP card after the system has been suspended
STEPS:
1. Click "Test" and insert a MSP card into the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
2. Do not remove the device after this test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: mediacard/msp-storage-after-suspend
estimated_duration: 10.0
depends: mediacard/msp-insert-after-suspend
user: root
command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
_description:
This test is automated and executes after the mediacard/msp-insert-after-suspend test
is run. It tests reading and writing to the MSP card after the system has been suspended.
plugin: user-interact
id: mediacard/msp-remove-after-suspend
estimated_duration: 30.0
depends: mediacard/msp-insert-after-suspend
command: removable_storage_watcher --memorycard remove sdio usb scsi
_description:
PURPOSE:
This test will check that the system correctly detects the removal
of a MSP card from the systems card reader after the system has been suspended.
STEPS:
1. Click "Test" and remove the MSP card from the reader.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: user-interact
id: mediacard/xd-insert-after-suspend
estimated_duration: 30.0
depends: suspend/suspend_advanced
command: removable_storage_watcher --memorycard insert sdio usb scsi
_description:
PURPOSE:
This test will check that the systems media card reader can
detect the insertion of a xD card after the system has been suspended
STEPS:
1. Click "Test" and insert a xD card into the reader.
If a file browser opens up, you can safely close it.
(Note: this test will time-out after 20 seconds.)
2. Do not remove the device after this test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: mediacard/xd-storage-after-suspend
estimated_duration: 10.0
depends: mediacard/xd-insert-after-suspend
user: root
command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
_description:
This test is automated and executes after the mediacard/xd-insert-after-suspend test
is run. It tests reading and writing to the xD card after the system has been suspended.
plugin: user-interact
id: mediacard/xd-remove-after-suspend
estimated_duration: 30.0
depends: mediacard/xd-insert-after-suspend
command: removable_storage_watcher --memorycard remove sdio usb scsi
_description:
PURPOSE:
This test will check that the system correctly detects the removal
of a xD card from the systems card reader after the system has been suspended.
STEPS:
1. Click "Test" and remove the xD card from the reader.
(Note: this test will time-out after 20 seconds.)
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
plugin: shell
id: touchpad/touchpad_after_suspend
depends: suspend/suspend_advanced_auto
requires:
dmi.product in ['Notebook','Laptop','Portable']
xinput.device_class == 'XITouchClass' and xinput.touch_mode != 'dependent'
command: true
estimated_duration: 1.2
_description:
Determine if the touchpad is still functioning after suspend/resume.
plugin: manual
id: touchscreen/touchscreen_after_suspend
depends: suspend/suspend_advanced_auto
estimated_duration: 30.0
_description:
PURPOSE:
Check touchscreen tap recognition
STEPS:
1. Tap an object on the screen with finger. The cursor should jump to location tapped and object should highlight
VERIFICATION:
Does tap recognition work?
|