Project Number Date
test_Tails_ISO_stable 5506 10 Mar 2025, 18:51

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:38.791 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:15.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 37.469
When I start Tails from USB drive "old" with network unplugged 1:32.339
Then the boot device has safe access rights 3.241
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.331
After features/support/hooks.rb:330 3.549
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.291
And I start Tails from USB drive "old" with network unplugged and I login 1:25.972
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 32.526
And I take note of which tps features are available 1.439
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.767
After features/support/hooks.rb:330 0.211
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.601
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.243
Then Tails is running from USB drive "old" 0.746
And all tps features are active 2.014
When I write some files expected to persist 1.802
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.762
And I take note of which tps features are available 0.416
And I shutdown Tails and wait for the computer to power off 4.242
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.571
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.011
Tags: @product
2:30.560
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 without a persistent partition and stopped at Tails Greeter's login screen 11.751
And I log in to a new session 18.015
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.701
And I plug USB drive "to_upgrade" 3.585
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.287
Then the running Tails is installed on USB drive "to_upgrade" 18.723
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:330 0.826
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.601
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.623
Then all tps features from the old Tails version are active 1.671
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.566
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.578
After features/support/hooks.rb:330 1.432
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:50.478
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.551
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.633
When the network is plugged 0.090
And Tor is ready 20.533
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.202
Given I shutdown Tails and wait for the computer to power off 1:18.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.322
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.281
# 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.261
When the network is plugged 0.069
And Tor is ready 19.410
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.215
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.859
Given I shutdown Tails and wait for the computer to power off 6.701
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.328
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.107
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.165
# 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.370
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.422
When the network is plugged 0.074
And Tor is ready 19.348
Then the Upgrader considers the system as up-to-date 0.340
# 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.454
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.989
After features/support/hooks.rb:330 0.841
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
37.792
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 10.173
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.055
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.141
And Tor is ready 20.266
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.593
After features/support/hooks.rb:330 0.755
After features/support/hooks.rb:100 0.000