Project Number Date
test_Tails_ISO_devel 3794 29 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:44.778 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:23.873
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 37.489
When I start Tails from USB drive "old" with network unplugged 1:40.649
Then the boot device has safe access rights 3.332
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 7.131
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.804
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:33.847
Then Tails is running from USB drive "old" 0.464
And I create a persistent partition 30.461
And I take note of which tps features are available 2.442
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.606
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.141
Then Tails is running from USB drive "old" 0.344
And all tps features are active 2.066
When I write some files expected to persist 1.959
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.532
And all persistent directories from the old Tails version have safe access rights 3.173
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.255
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.339
After features/support/hooks.rb:330 0.112
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.513
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.608
And I log in to a new session 20.903
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.089
And I plug USB drive "to_upgrade" 2.490
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.529
Then the running Tails is installed on USB drive "to_upgrade" 25.488
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 2.598
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.850
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.582
Then all tps features from the old Tails version are active 1.767
And Tails is running from USB drive "to_upgrade" 0.431
And the boot device has safe access rights 3.786
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.644
After features/support/hooks.rb:330 1.143
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:32.598
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.201
And no SquashFS delta is installed 0.347
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.620
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.392
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.121
And Tor is ready 18.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.147
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.922
Given I shutdown Tails and wait for the computer to power off 8.699
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.511
Then Tails is running version 6.2~testoverlayfs 0.051
And all tps features are active 2.132
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
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.307
# 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.281
When the network is plugged 0.070
And Tor is ready 18.486
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.953
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.103
Given I shutdown Tails and wait for the computer to power off 4.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.111
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.889
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.069
And Tor is ready 20.620
Then the Upgrader considers the system as up-to-date 0.303
# 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.796
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.950
After features/support/hooks.rb:330 0.731
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.445
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 10.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
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.142
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 19.834
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.816
After features/support/hooks.rb:330 0.858
After features/support/hooks.rb:100 0.000