Project Number Date
test_Tails_ISO_devel 3709 25 Feb 2025, 13:03

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:49.650 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:7.082
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 32.744
When I start Tails from USB drive "old" with network unplugged 1:27.641
Then the boot device has safe access rights 4.278
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 14.591
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.157
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login 1:24.659
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 32.145
And I take note of which tps features are available 1.315
Then a Tails persistence partition exists on USB drive "old" 0.913
And I shutdown Tails and wait for the computer to power off 8.564
After features/support/hooks.rb:330 0.243
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.428
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.663
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.351
When I write some files expected to persist 2.197
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.386
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.526
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 6.339
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.461
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.346
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.618
And I log in to a new session 18.871
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.605
And I plug USB drive "to_upgrade" 2.707
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.137
Then the running Tails is installed on USB drive "to_upgrade" 19.987
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 2.041
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.243
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.330
Then all tps features from the old Tails version are active 1.632
And Tails is running from USB drive "to_upgrade" 0.469
And the boot device has safe access rights 3.618
And the expected persistent files created with the old Tails version are present in the filesystem 1.527
And all persistent directories from the old Tails version have safe access rights 2.468
After features/support/hooks.rb:330 1.578
After features/support/hooks.rb:100 0.019
6:42.967
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.066
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.093
And Tor is ready 18.310
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.003
Given I shutdown Tails and wait for the computer to power off 13.632
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.528
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.340
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# 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.284
When the network is plugged 0.069
And Tor is ready 16.933
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.870
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.426
Given I shutdown Tails and wait for the computer to power off 4.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.153
Then Tails is running version 6.3~testoverlayfs 0.029
And all tps features are active 2.198
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.073
And Tor is ready 19.743
Then the Upgrader considers the system as up-to-date 0.321
# 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 14.501
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.946
After features/support/hooks.rb:330 0.763
After features/support/hooks.rb:100 0.048
57.424
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 9.686
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.047
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 46.555
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.671
After features/support/hooks.rb:330 0.989
After features/support/hooks.rb:100 0.000