Project Number Date
test_Tails_ISO_devel 3753 25 Mar 2025, 13:20

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 18:59.777 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
1:55.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.652
When I start Tails from USB drive "old" with network unplugged 1:21.531
Then the boot device has safe access rights 2.887
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.095
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:330 3.538
After features/support/hooks.rb:100 0.011
Tags: @product
2:2.680
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:20.358
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 31.274
And I take note of which tps features are available 1.380
Then a Tails persistence partition exists on USB drive "old" 0.760
And I shutdown Tails and wait for the computer to power off 8.384
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.237
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.384
Then Tails is running from USB drive "old" 0.345
And all tps features are active 1.823
When I write some files expected to persist 1.960
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.325
And I take note of which tps features are available 0.390
And I shutdown Tails and wait for the computer to power off 4.277
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.955
After features/support/hooks.rb:330 0.092
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.199
And I log in to a new session 17.483
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.388
Then the running Tails is installed on USB drive "to_upgrade" 20.673
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 1.836
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.609
Then all tps features from the old Tails version are active 1.746
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.196
And the expected persistent files created with the old Tails version are present in the filesystem 1.331
And all persistent directories from the old Tails version have safe access rights 2.281
After features/support/hooks.rb:330 1.454
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:48.582
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.029
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.441
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.068
And Tor is ready 53.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.540
Given I shutdown Tails and wait for the computer to power off 8.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.820
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.090
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.274
# 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.264
When the network is plugged 0.110
And Tor is ready 19.759
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.843
Given I shutdown Tails and wait for the computer to power off 4.668
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.666
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.862
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.268
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.078
And Tor is ready 20.302
Then the Upgrader considers the system as up-to-date 0.308
# 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 14.454
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.973
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.994
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
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.117
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 23.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.942
After features/support/hooks.rb:330 0.595
After features/support/hooks.rb:100 0.000