Project Number Date
test_Tails_ISO_stable 5499 06 Mar 2025, 13:43

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:8.414 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:14.328
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 32.039
When I start Tails from USB drive "old" with network unplugged 1:36.400
Then the boot device has safe access rights 3.414
And Tails is running from USB drive "old" 0.419
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 8.786
After features/support/hooks.rb:100 0.010
Tags: @product
2:25.408
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login 1:39.434
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 34.457
And I take note of which tps features are available 1.605
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 8.394
After features/support/hooks.rb:330 0.277
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.520
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.657
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.163
When I write some files expected to persist 2.005
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.318
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.518
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.300
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.151
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.340
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 12.595
And I log in to a new session 18.378
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.578
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.786
Then the running Tails is installed on USB drive "to_upgrade" 24.175
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 3.760
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.011
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.790
Then all tps features from the old Tails version are active 2.058
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.405
And the expected persistent files created with the old Tails version are present in the filesystem 1.551
And all persistent directories from the old Tails version have safe access rights 2.595
After features/support/hooks.rb:330 1.271
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:46.168
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.428
And no SquashFS delta is installed 0.429
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.498
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.083
And Tor is ready 24.909
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.272
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.811
Given I shutdown Tails and wait for the computer to power off 11.654
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.701
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 3.348
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.330
When the network is plugged 0.123
And Tor is ready 20.160
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.878
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.949
Given I shutdown Tails and wait for the computer to power off 4.396
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.354
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.728
And the file system changes introduced in version 6.3~testoverlayfs are present 0.696
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.442
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.582
When the network is plugged 0.088
And Tor is ready 23.003
Then the Upgrader considers the system as up-to-date 0.327
# 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 17.235
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.034
After features/support/hooks.rb:330 0.755
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.636
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 12.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 20.046
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.872
After features/support/hooks.rb:330 1.974
After features/support/hooks.rb:100 0.000