Project Number Date
test_Tails_ISO_stable 5646 13 May 2025, 22:42

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:39.425 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:27.535
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 35.610
When I start Tails from USB drive "old" with network unplugged 1:45.829
Then the boot device has safe access rights 3.609
And Tails is running from USB drive "old" 0.401
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.383
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 13.530
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.784
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:39.269
Then Tails is running from USB drive "old" 0.443
And I create a persistent partition 36.520
And I take note of which tps features are available 2.521
Then a Tails persistence partition exists on USB drive "old" 0.900
And I shutdown Tails and wait for the computer to power off 8.895
After features/support/hooks.rb:330 0.193
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.970
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.704
Then Tails is running from USB drive "old" 0.404
And all tps features are active 2.288
When I write some files expected to persist 3.079
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.529
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 6.673
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.857
After features/support/hooks.rb:330 0.110
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.342
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 12.091
And I log in to a new session 22.209
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.031
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.443
Then the running Tails is installed on USB drive "to_upgrade" 21.670
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 7.658
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.079
Then all tps features from the old Tails version are active 1.874
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.237
And the expected persistent files created with the old Tails version are present in the filesystem 1.511
And all persistent directories from the old Tails version have safe access rights 2.528
After features/support/hooks.rb:330 2.703
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:48.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.712
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.354
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.076
And Tor is ready 22.124
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.164
Given I shutdown Tails and wait for the computer to power off 11.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.639
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.357
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.110
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.260
When the network is plugged 0.081
And Tor is ready 13.797
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.402
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.152
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.859
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.248
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.081
And Tor is ready 19.139
Then the Upgrader considers the system as up-to-date 0.358
# 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.988
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.075
After features/support/hooks.rb:330 0.824
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.658
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 9.954
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.585
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.374
After features/support/hooks.rb:330 1.121
After features/support/hooks.rb:100 0.000