Project Number Date
test_Tails_ISO_devel 3769 07 Apr 2025, 13:18

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:6.220 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:5.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.276
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 32.904
When I start Tails from USB drive "old" with network unplugged 1:27.192
Then the boot device has safe access rights 3.098
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.240
After features/support/hooks.rb:330 9.770
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.902
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:27.665
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 32.120
And I take note of which tps features are available 1.973
Then a Tails persistence partition exists on USB drive "old" 0.963
And I shutdown Tails and wait for the computer to power off 8.632
After features/support/hooks.rb:330 0.214
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.364
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.975
Then Tails is running from USB drive "old" 0.418
And all tps features are active 2.580
When I write some files expected to persist 2.109
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.616
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 6.532
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.686
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.322
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 without a persistent partition and stopped at Tails Greeter's login screen 13.627
And I log in to a new session 22.406
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.142
And I plug USB drive "to_upgrade" 2.549
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.865
Then the running Tails is installed on USB drive "to_upgrade" 28.311
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 2.304
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.893
Then all tps features from the old Tails version are active 1.654
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.294
And the expected persistent files created with the old Tails version are present in the filesystem 1.724
And all persistent directories from the old Tails version have safe access rights 2.667
After features/support/hooks.rb:330 1.328
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:48.373
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 13.528
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.488
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.578
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.664
When the network is plugged 0.077
And Tor is ready 22.614
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.960
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.917
Given I shutdown Tails and wait for the computer to power off 11.149
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.623
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.530
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.324
When the network is plugged 0.079
And Tor is ready 19.346
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.635
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.659
Given I shutdown Tails and wait for the computer to power off 4.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.187
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 1.944
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.342
When the network is plugged 0.085
And Tor is ready 20.646
Then the Upgrader considers the system as up-to-date 0.309
# 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 16.598
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.719
After features/support/hooks.rb:330 0.777
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
40.696
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.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.004
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.146
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 21.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.830
After features/support/hooks.rb:330 1.398
After features/support/hooks.rb:100 0.000