Project Number Date
test_Tails_ISO_devel 3742 17 Mar 2025, 17:22

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:29.398 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:12.222
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.298
When I start Tails from USB drive "old" with network unplugged 1:34.859
Then the boot device has safe access rights 3.623
And Tails is running from USB drive "old" 0.386
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.377
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 3.929
After features/support/hooks.rb:100 0.014
Tags: @product
2:18.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.680
And I start Tails from USB drive "old" with network unplugged and I login 1:35.141
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 31.790
And I take note of which tps features are available 1.467
Then a Tails persistence partition exists on USB drive "old" 0.867
And I shutdown Tails and wait for the computer to power off 8.146
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.011
Tags: @product
2:58.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.708
Then Tails is running from USB drive "old" 0.812
And all tps features are active 2.330
When I write some files expected to persist 2.175
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.864
And I take note of which tps features are available 1.304
And I shutdown Tails and wait for the computer to power off 6.695
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.310
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.392
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 without a persistent partition and stopped at Tails Greeter's login screen 11.807
And I log in to a new session 19.816
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.724
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.591
Then the running Tails is installed on USB drive "to_upgrade" 23.556
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 4.762
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.117
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.670
Then all tps features from the old Tails version are active 1.908
And Tails is running from USB drive "to_upgrade" 0.495
And the boot device has safe access rights 3.574
And the expected persistent files created with the old Tails version are present in the filesystem 1.593
And all persistent directories from the old Tails version have safe access rights 2.648
After features/support/hooks.rb:330 1.474
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:8.519
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 17.137
And no SquashFS delta is installed 1.438
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.481
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.507
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.553
When the network is plugged 0.079
And Tor is ready 23.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.863
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.812
Given I shutdown Tails and wait for the computer to power off 8.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.372
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.344
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.318
When the network is plugged 0.106
And Tor is ready 19.327
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.233
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.269
Given I shutdown Tails and wait for the computer to power off 4.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.995
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.637
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.641
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.330
When the network is plugged 0.067
And Tor is ready 48.799
Then the Upgrader considers the system as up-to-date 0.300
# 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.034
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.070
After features/support/hooks.rb:330 0.714
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
43.559
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 11.976
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.772
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 24.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.201
After features/support/hooks.rb:330 0.799
After features/support/hooks.rb:100 0.000