Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 19 13 Dec 2024, 17:31

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 20:31.868 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:7.862
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.400
When I start Tails from USB drive "old" with network unplugged 1:33.072
Then the boot device has safe access rights 3.054
And Tails is running from USB drive "old" 0.379
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 6.822
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.826
Before features/support/hooks.rb:269 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:39.270
Then Tails is running from USB drive "old" 0.410
And I create a persistent partition 42.734
And I take note of which tps features are available 1.981
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.395
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.611
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.164
Then Tails is running from USB drive "old" 1.233
And all tps features are active 1.874
When I write some files expected to persist 1.718
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.810
And all persistent directories from the old Tails version have safe access rights 3.400
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.263
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.245
After features/support/hooks.rb:326 0.133
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.662
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.250
And I log in to a new session 18.706
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.360
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.441
Then the running Tails is installed on USB drive "to_upgrade" 25.058
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 1.968
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.850
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.742
Then all tps features from the old Tails version are active 1.665
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.666
And the expected persistent files created with the old Tails version are present in the filesystem 1.461
And all persistent directories from the old Tails version have safe access rights 2.742
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:0.358
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.641
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.565
When the network is plugged 0.146
And Tor is ready 26.198
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.867
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.728
Given I shutdown Tails and wait for the computer to power off 11.153
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.101
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.098
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.399
When the network is plugged 0.219
And Tor is ready 16.973
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.640
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.053
Given I shutdown Tails and wait for the computer to power off 4.221
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.740
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.072
And Tor is ready 18.074
Then the Upgrader considers the system as up-to-date 10.877
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 15.479
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.177
After features/support/hooks.rb:326 0.813
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
42.696
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.476
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.043
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.992
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 23.617
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.436
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.000