Project Number Date
test_Tails_ISO_devel 3801 05 May 2025, 18:48

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:48.564 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:18.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 32.102
When I start Tails from USB drive "old" with network unplugged 1:40.438
Then the boot device has safe access rights 3.345
And Tails is running from USB drive "old" 0.441
And there is no persistence partition on USB drive "old" 0.107
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.239
After features/support/hooks.rb:330 3.522
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.621
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:25.477
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 33.436
And I take note of which tps features are available 1.847
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 8.464
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.007
Tags: @product
3:19.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.710
Then Tails is running from USB drive "old" 0.904
And all tps features are active 4.827
When I write some files expected to persist 2.139
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 3.050
And I take note of which tps features are available 0.552
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.066
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.028
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.627
And I log in to a new session 21.944
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.794
And I plug USB drive "to_upgrade" 2.519
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.176
Then the running Tails is installed on USB drive "to_upgrade" 31.444
And I unplug USB drive "to_upgrade" 0.292
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:330 3.140
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.565
Then all tps features from the old Tails version are active 1.851
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.672
And the expected persistent files created with the old Tails version are present in the filesystem 1.741
And all persistent directories from the old Tails version have safe access rights 3.018
After features/support/hooks.rb:330 1.456
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:54.862
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 15.517
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.071
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.383
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.074
And Tor is ready 22.531
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.976
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.136
Given I shutdown Tails and wait for the computer to power off 8.807
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.730
Then Tails is running version 6.2~testoverlayfs 0.086
And all tps features are active 6.560
And the file system changes introduced in version 6.2~testoverlayfs are present 1.121
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.801
When the network is plugged 0.071
And Tor is ready 20.744
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.409
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.684
Given I shutdown Tails and wait for the computer to power off 6.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.124
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.318
And the file system changes introduced in version 6.3~testoverlayfs are present 0.574
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.252
And Tor is ready 20.175
Then the Upgrader considers the system as up-to-date 0.328
# 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.459
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.578
After features/support/hooks.rb:330 0.861
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
43.659
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 15.502
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.006
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 21.389
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.459
After features/support/hooks.rb:330 0.799
After features/support/hooks.rb:100 0.000