Project Number Date
test_Tails_ISO_stable 5562 09 Apr 2025, 13:50

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:58.138 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:11.222
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.408
When I start Tails from USB drive "old" with network unplugged 1:34.194
Then the boot device has safe access rights 3.274
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:330 3.704
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.478
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 "old" with network unplugged and I login 1:37.128
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 31.877
And I take note of which tps features are available 1.701
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 8.342
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.002
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.277
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.023
Then Tails is running from USB drive "old" 0.369
And all tps features are active 2.045
When I write some files expected to persist 1.788
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.534
And all persistent directories from the old Tails version have safe access rights 2.380
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.303
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.509
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.032
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 without a persistent partition and stopped at Tails Greeter's login screen 11.187
And I log in to a new session 18.307
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.780
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.490
Then the running Tails is installed on USB drive "to_upgrade" 23.457
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 0.821
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.593
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.975
Then all tps features from the old Tails version are active 1.574
And Tails is running from USB drive "to_upgrade" 0.405
And the boot device has safe access rights 3.366
And the expected persistent files created with the old Tails version are present in the filesystem 1.708
And all persistent directories from the old Tails version have safe access rights 2.389
After features/support/hooks.rb:330 1.250
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:4.718
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 with a persistent partition enabled and logged in 12.588
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.061
And Tor is ready 22.776
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.349
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.262
Given I shutdown Tails and wait for the computer to power off 8.760
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.777
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.285
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# 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.361
When the network is plugged 0.370
And Tor is ready 47.347
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.593
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.901
Given I shutdown Tails and wait for the computer to power off 4.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.904
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.957
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.080
And Tor is ready 16.677
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.332
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.513
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
39.089
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 11.566
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.675
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 19.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.022
After features/support/hooks.rb:330 0.623
After features/support/hooks.rb:100 0.000