Project Number Date
test_Tails_ISO_20872-more-gtk-launch 2 27 Mar 2025, 18:08

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:17.574 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:23.627
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 36.135
When I start Tails from USB drive "old" with network unplugged 1:41.623
Then the boot device has safe access rights 3.499
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 3.581
After features/support/hooks.rb:100 0.013
Tags: @product
2:8.299
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:25.237
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 31.511
And I take note of which tps features are available 1.507
Then a Tails persistence partition exists on USB drive "old" 0.926
And I shutdown Tails and wait for the computer to power off 8.564
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.012
Tags: @product
3:1.096
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.299
Then Tails is running from USB drive "old" 1.673
And all tps features are active 2.202
When I write some files expected to persist 2.116
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 3.186
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 6.222
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.968
After features/support/hooks.rb:330 0.112
After features/support/hooks.rb:100 0.011
Tags: @product
2:56.057
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 without a persistent partition and stopped at Tails Greeter's login screen 24.920
And I log in to a new session 22.007
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.884
And I plug USB drive "to_upgrade" 2.508
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.756
Then the running Tails is installed on USB drive "to_upgrade" 25.525
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 2.132
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.358
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.163
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 3.497
And the expected persistent files created with the old Tails version are present in the filesystem 1.595
And all persistent directories from the old Tails version have safe access rights 2.572
After features/support/hooks.rb:330 1.939
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:29.610
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 with a persistent partition enabled and logged in 25.100
And no SquashFS delta is installed 0.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.407
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.537
When the network is plugged 0.093
And Tor is ready 20.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.630
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.785
Given I shutdown Tails and wait for the computer to power off 11.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:32.113
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 3.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.419
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.368
When the network is plugged 0.585
And Tor is ready 21.178
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.138
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.541
Given I shutdown Tails and wait for the computer to power off 4.828
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.382
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.292
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.270
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.107
And Tor is ready 19.897
Then the Upgrader considers the system as up-to-date 0.325
# 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.365
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.946
After features/support/hooks.rb:330 0.834
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
47.524
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 17.210
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
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.065
But a current signing key is available on our website 0.000
When the network is plugged 0.315
And Tor is ready 20.853
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.635
After features/support/hooks.rb:330 1.435
After features/support/hooks.rb:100 0.000