Project Number Date
test_Tails_ISO_stable 5554 04 Apr 2025, 13:16

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:59.188 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:32.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.264
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 35.598
When I start Tails from USB drive "old" with network unplugged 1:51.106
Then the boot device has safe access rights 3.356
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.472
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.761
After features/support/hooks.rb:100 0.010
Tags: @product
2:25.719
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:40.117
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 32.966
And I take note of which tps features are available 2.468
Then a Tails persistence partition exists on USB drive "old" 1.036
And I shutdown Tails and wait for the computer to power off 8.522
After features/support/hooks.rb:330 0.281
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.064
Then Tails is running from USB drive "old" 1.607
And all tps features are active 1.987
When I write some files expected to persist 2.336
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 2.483
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 6.532
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.201
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.623
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.752
And I log in to a new session 19.681
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.744
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.233
Then the running Tails is installed on USB drive "to_upgrade" 22.328
And I unplug USB drive "to_upgrade" 0.260
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.228
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.116
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.158
Then all tps features from the old Tails version are active 1.681
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 3.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.448
And all persistent directories from the old Tails version have safe access rights 2.611
After features/support/hooks.rb:330 1.595
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:56.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.987
And no SquashFS delta is installed 0.710
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.598
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.062
And Tor is ready 22.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.315
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.804
Given I shutdown Tails and wait for the computer to power off 8.815
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.094
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.360
And the file system changes introduced in version 6.2~testoverlayfs are present 0.422
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.251
When the network is plugged 0.070
And Tor is ready 19.454
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.686
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.713
Given I shutdown Tails and wait for the computer to power off 4.316
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.565
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.111
And the file system changes introduced in version 6.3~testoverlayfs are present 0.652
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.350
When the network is plugged 0.075
And Tor is ready 17.784
Then the Upgrader considers the system as up-to-date 0.292
# 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 16.624
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.669
After features/support/hooks.rb:330 0.750
After features/support/hooks.rb:100 0.091
Tags: @product @automatic_upgrade
1:2.810
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.242
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.482
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.152
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 51.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.655
After features/support/hooks.rb:330 1.088
After features/support/hooks.rb:100 0.000