Project Number Date
test_Tails_ISO_devel 3774 10 Apr 2025, 11:40

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 21:44.983 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:24.822
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.236
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 36.228
When I start Tails from USB drive "old" with network unplugged 1:42.530
Then the boot device has safe access rights 3.609
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:330 11.039
After features/support/hooks.rb:100 0.044
Tags: @product
2:37.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.314
And I start Tails from USB drive "old" with network unplugged and I login 1:49.295
Then Tails is running from USB drive "old" 0.409
And I create a persistent partition 35.964
And I take note of which tps features are available 2.292
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.907
After features/support/hooks.rb:330 0.191
After features/support/hooks.rb:100 0.019
Tags: @product
3:19.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.267
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.921
Then Tails is running from USB drive "old" 1.139
And all tps features are active 2.437
When I write some files expected to persist 4.612
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.474
And all persistent directories from the old Tails version have safe access rights 3.389
And I take note of which tps features are available 0.648
And I shutdown Tails and wait for the computer to power off 7.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.002
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.371
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 11.451
And I log in to a new session 20.553
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.723
And I plug USB drive "to_upgrade" 2.577
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.726
Then the running Tails is installed on USB drive "to_upgrade" 23.837
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.268
After features/support/hooks.rb:330 0.970
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.585
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.535
Then all tps features from the old Tails version are active 1.958
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.629
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 3.254
After features/support/hooks.rb:330 1.584
After features/support/hooks.rb:100 0.012
7:38.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.200
And no SquashFS delta is installed 0.252
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.709
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.505
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.106
And Tor is ready 21.136
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.033
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.766
Given I shutdown Tails and wait for the computer to power off 10.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.508
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.789
And the file system changes introduced in version 6.2~testoverlayfs are present 0.371
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.360
# 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.341
When the network is plugged 0.080
And Tor is ready 19.197
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.095
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.366
Given I shutdown Tails and wait for the computer to power off 4.685
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:30.670
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.287
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.379
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.093
And Tor is ready 23.789
Then the Upgrader considers the system as up-to-date 0.341
# 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 17.262
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.591
After features/support/hooks.rb:330 1.065
After features/support/hooks.rb:100 0.024
41.135
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.591
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.450
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 22.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.289
After features/support/hooks.rb:330 0.715
After features/support/hooks.rb:100 0.000