Project Number Date
test_Tails_ISO_stable 5596 24 Apr 2025, 15:45

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:47.509 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:13.273
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 36.462
When I start Tails from USB drive "old" with network unplugged 1:31.197
Then the boot device has safe access rights 3.256
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:330 3.804
After features/support/hooks.rb:100 0.013
Tags: @product
2:10.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:26.533
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 32.373
And I take note of which tps features are available 1.690
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 8.519
After features/support/hooks.rb:330 0.196
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.407
Then Tails is running from USB drive "old" 0.945
And all tps features are active 2.008
When I write some files expected to persist 1.714
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.515
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 6.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.854
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 24.406
And I log in to a new session 19.135
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.028
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.274
Then the running Tails is installed on USB drive "to_upgrade" 29.886
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 1.072
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.737
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.577
Then all tps features from the old Tails version are active 1.746
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.836
And the expected persistent files created with the old Tails version are present in the filesystem 1.529
And all persistent directories from the old Tails version have safe access rights 2.508
After features/support/hooks.rb:330 1.170
After features/support/hooks.rb:100 0.011
6:39.734
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 11.509
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.510
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.077
And Tor is ready 20.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.070
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.310
Given I shutdown Tails and wait for the computer to power off 8.711
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.099
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.163
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.296
When the network is plugged 0.094
And Tor is ready 18.423
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.055
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.840
Given I shutdown Tails and wait for the computer to power off 4.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.203
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.056
And the file system changes introduced in version 6.3~testoverlayfs are present 0.626
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.368
When the network is plugged 0.075
And Tor is ready 19.720
Then the Upgrader considers the system as up-to-date 0.334
# 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.435
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.522
After features/support/hooks.rb:330 0.774
After features/support/hooks.rb:100 0.043
39.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.934
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.623
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 21.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.855
After features/support/hooks.rb:330 0.825
After features/support/hooks.rb:100 0.000