401
by Michael Vogt
create (minimal) testing documentation |
1 |
This applet has no unittests (yet). |
2 |
||
3 |
In order to test changes you need to kill update-notifier from your |
|
4 |
running session (there can only be one) and start it from your local |
|
5 |
build dir. Make sure you build with --prefix=/usr (or some other |
|
464.1.9
by seb128
clean libglade use |
6 |
location where your ui files are). Then you can do the |
401
by Michael Vogt
create (minimal) testing documentation |
7 |
following: |
8 |
||
9 |
Test updates: |
|
10 |
Install a package from a previous version and check if update-notifier |
|
11 |
detects that and shows a update icon. Run apt-get update and check if |
|
12 |
it detects that a package manager is running. |
|
13 |
||
14 |
Test hooks: |
|
15 |
Copy a example hook file into /usr/lib/update-notifier/user.d/ (or |
|
16 |
touch it) and touch /var/lib/update-notifier/dpkg-run-stamp to trigger |
|
17 |
it reading the hooks. Modify ~/.update-notifier/hooks_seen to |
|
18 |
simulate certain conditions. Add identical files to "user.d" to test |
|
19 |
the duplicates detection. |
|
20 |
||
21 |
Test reboot notification: |
|
22 |
Run /usr/share/update-notifier/notify-reboot-required and then do |
|
23 |
touch /var/lib/update-notifier/dpkg-run-stamp. |
|
24 |
||
25 |
Test cdrom detection: |
|
456
by Michael Vogt
README.testing: add faketime based testing for autolaunch |
26 |
Put a ubuntu CD into the driver and verify that its detected. |
27 |
||
28 |
Test auto-launch: |
|
29 |
The "faketime" package is useful for testing the auto-launch |
|
30 |
funtionatliy
|
|
31 |
$ NO_FAKE_STAT=1 faketime '10 days' update-notifier --debug-updates |
|
32 |
# aftwards the launch time in u-m needs to be reset
|
|
33 |
$ gconftool --unset /apps/update-manager/launch_time |