Project Number Date
test_Tails_ISO_stable 5765 09 Jul 2025, 14:02

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:17.468 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
1:55.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.627
When I start Tails from USB drive "old" with network unplugged 1:20.908
Then the boot device has safe access rights 3.397
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 3.856
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:24.831
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 31.485
And I take note of which tps features are available 2.056
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.747
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.599
Then Tails is running from USB drive "old" 0.398
And all tps features are active 2.350
When I write some files expected to persist 1.778
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.286
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.510
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 4.428
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.529
After features/support/hooks.rb:330 0.118
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.164
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 10.437
And I log in to a new session 18.233
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.703
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.082
Then the running Tails is installed on USB drive "to_upgrade" 26.771
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.262
After features/support/hooks.rb:330 0.708
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.626
Then all tps features from the old Tails version are active 1.873
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.392
And the expected persistent files created with the old Tails version are present in the filesystem 1.384
And all persistent directories from the old Tails version have safe access rights 2.249
After features/support/hooks.rb:330 1.036
After features/support/hooks.rb:100 0.009
6:37.295
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 11.383
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.081
And Tor is ready 23.206
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.199
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.386
Given I shutdown Tails and wait for the computer to power off 8.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.444
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.461
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.342
When the network is plugged 0.102
And Tor is ready 18.088
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.167
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.127
Given I shutdown Tails and wait for the computer to power off 6.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.605
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.952
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.068
And Tor is ready 21.279
Then the Upgrader considers the system as up-to-date 0.322
# 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.596
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.637
After features/support/hooks.rb:330 0.693
After features/support/hooks.rb:100 0.019
40.103
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 10.780
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.138
And Tor is ready 21.986
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.759
After features/support/hooks.rb:330 0.901
After features/support/hooks.rb:100 0.000