Testing Papercuts
Comments
 Share
 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUV
1
Test NameActionStatusCommentsBug #('s)
2
audio/list_devicesKeepAutomated
3
audio/alsa_record_playback_externalFixFixedAll the playback tests should make an effort to set the mixer settings correctly prior to running the test. Seems fairly straightforward to do this from PulseAudio command line 'pacmd'https://bugs.launchpad.net/checkbox/+bug/916859
4
audio/alsa_record_playback_internalFix
5
audio/alsa_record_playback_usbFix
6
audio/alsa_record_playback_automatedFix
7
audio/playback_autoFix
8
audio/playback_headphonesFix
9
bluetooth/detect
10
bluetooth/detect-outputAutomated test
11
bluetooth/audio
12
bluetooth/browse-files
13
bluetooth/file-transfer
14
bluetooth/keyboard
15
bluetooth/mouse
16
camera/detectKeep
17
camera/stillKeep
18
camera/videoFixFixedVideo comes out jerky and stuttering. Could be confusing for testers.https://bugs.launchpad.net/checkbox/+bug/912683Replace with camera/display (with increased timeout)
19
cpu/scaling_testAutomated test
20
cpu/offlining_testAutomated test
21
cpu/topologyAutomated test
22
cpu/frequency_governorsAutomated test
23
cpu/clocktestAutomated test
24
disk/detectAutomated test
25
disk/benchmarksAutomated test
26
disk/read_performanceAutomated test
27
disk/smartAutomated test
28
disk/storage_devicesAutomated test
29
disk/max_diskspace_usedAutomated test
30
firewire/hddFixFixedRather than asking the user to manually perform file operations, we should look into doing this in a more automated fashion, like the USB drive tests. Firewire automounting and displaying on the desktop can be also tested within a script.Have an insert,store,remove test for each type of media (usb, mediacard, firewire, optical) and run each in turn.For now, changed usb_test to removable_storage_test and that should work for firewire as well as usb. need to add insert/remove tests possibly...
31
floppy/checkAutomated test
32
graphics/glxgears
33
graphics/xorg-versionAutomated test
34
graphics/gtkperfAutomated test
35
graphics/compiz_checkAutomated test
36
graphics/display
37
graphics/minimum_resolutionAutomated test
38
graphics/xorg-memoryAutomated test
39
graphics/xorg-failsafeAutomated test
40
graphics/xorg-processAutomated test
41
graphics/cycle_resolution
42
graphics/xrandr_detect_modesFixFixedWithout a detailed spec sheet for the monitor and video card it's hard to determine if all possible modes are listed. I'd turn this into an automated test that fails if the screen is detected as Unknown or using the VESA drivers. Should we have a test which checks if vesa drivers are being used?Write a data gathering test to find out what the meaning of an 'unknown' display isFor now, just check if vesa drivers are in use
Unknown monitor may be different in xorg logs, depends on gnome display and possibly on proprietary drivers modifications
43
info/screenshot
Replace• Very unreliable screenshot tool, always producing false positives. Need to find out why and see if there is a better solution.
44
input/mouse
45
input/keyboard
46
install/apt-get-gets-updatesAutomated test
47
keys/battery-info
48
keys/brightness
49
keys/media-controlFixFixedFinding a media file to play and then checking whether the keys work is cumbersome. "Test" should launch a small test script that actually listens for the media key events and displays them. I have some working code, I can produce something for this.https://code.launchpad.net/~roadmr/checkbox/interactive-media-keysSome keyboards just have play/prev/next. (e.g. logitech illuminated keyboard)
Perhaps should we remove the stop key from the list.
50
keys/mute
51
keys/sleep
52
keys/volume
53
keys/wireless
54
mediacard/mmcFixedThese should all really be automated in a similar fashion to the USB tests. As a side-note, adding insert/remove tests would also be good.
55
mediacard/mmc_after_suspend
56
mediacard/sd
57
mediacard/sd_after_suspend
58
mediacard/sdhc
59
mediacard/sdhc_after_suspend
60
memory/infoFixFixedThis displays bogus memory totals (as seen by kernel, rather than installed memory). Should be changed to extract total installed memory from DMI and could apply some heuristics to determine if memory as seen by the kernel makes sense, and pass/fail based on that.https://bugs.launchpad.net/checkbox/+bug/914882Automated test to compare output of DMI and /proc/meminfo
61
memory/checkAutomated test
62
miscellanea/fwts_testAutomated test
63
miscellanea/check_and_install_ipmitoolAutomated test
64
miscellanea/ipmi_testAutomated test
65
miscellanea/is_laptop
Automated test.
66
monitor/powersaving
67
monitor/displayportFix?FixedOutput from xrandr could be used to determine if a system has a particular video output, and whether to test it (via a requires:). Thus I don't have to test outputs my system doesn't have. This breaks if I'm using proprietary drivers (as e.g. the nvidia drivers don't show monitor information in xrandr).xrandr resource job to be created and requires added to jobs
68
monitor/dvi
69
monitor/hdmi
70
monitor/rca
71
monitor/svideo
72
monitor/vga
73
networking/detectAutomated test.
74
networking/bandwidthAutomated test.
75
networking/httpFixDoes fail on a Acer Aspire One during SRU testing. Need to find out why
76
networking/internetAutomated test.
77
networking/info
78
networking/multi_nicAutomated test.
79
networking/ntp
80
networking/pingFixDoes fail on a Acer Aspire One during SRU testing. Need to find out why
81
kAutomated test
82
optical/readFixFixed?No definition of what is 'appropriate'. DVDs and audio CDs don't work so we should say they shouldn't be used.
83
optical/cdrom-writeFixIn progress (bladernr)Description is too vague "Write something". Could be done automatically, just asking the user to insert appropriate media.
84
optical/dvd-writeFixIn progress (bladernr)
85
pcmcia-pcix/detect
86
power-management/lid
87
power-management/lid_close
88
power-management/lid_open
89
power-management/rtcAutomated test
90
power-management/shutdown-boot
91
power-management/tickless_idleAutomated test
92
power-management/fwts_wakealarmAutomated test
93
power-management/hibernate_advanced
94
stress/cpu_stress_testFixThis test has a fixed 2-hour duration, so at the very least the text should be amended to set the tester's expectations (i.e. system is unresponsive after 2 hours - maybe it crashed).Maybe rename the test to 'stress_two_hours'? Update the description
95
suspend/resolution_before_suspendAutomated test
96
suspend/audio_before_suspendAutomated test
97
suspend/cpu_before_suspendAutomated test
98
suspend/memory_before_suspendAutomated test
99
suspend/wireless_before_suspendAutomated test
100
suspend/bluetooth_obex_before_suspendAutomated test
Loading...
 
 
 
Tests