Project Number Date
test_Tails_ISO_20872-more-gtk-launch 6 31 Mar 2025, 07:50

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 19:13.729 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:1.751
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.182
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" 28.037
When I start Tails from USB drive "old" with network unplugged 1:28.280
Then the boot device has safe access rights 3.184
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 0.843
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:22.440
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 31.352
And I take note of which tps features are available 1.537
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 8.470
After features/support/hooks.rb:330 0.172
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.925
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.485
Then Tails is running from USB drive "old" 0.522
And all tps features are active 2.092
When I write some files expected to persist 1.671
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.845
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.194
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.835
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.208
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.149
And I log in to a new session 19.156
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.553
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.575
Then the running Tails is installed on USB drive "to_upgrade" 23.963
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.072
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.912
Then all tps features from the old Tails version are active 1.584
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.688
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.374
After features/support/hooks.rb:330 1.558
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:38.576
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.750
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.471
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.532
When the network is plugged 0.098
And Tor is ready 24.968
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.247
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.896
Given I shutdown Tails and wait for the computer to power off 8.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.000
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.139
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.282
# 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.240
When the network is plugged 0.076
And Tor is ready 20.614
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.452
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.813
Given I shutdown Tails and wait for the computer to power off 4.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.832
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.016
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.115
And Tor is ready 17.554
Then the Upgrader considers the system as up-to-date 0.301
# 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.670
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.728
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
40.671
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.348
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.128
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 23.308
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.315
After features/support/hooks.rb:330 0.715
After features/support/hooks.rb:100 0.000