Project Number Date
test_Tails_ISO_devel 3727 06 Mar 2025, 19:46

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:8.542 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:3.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.896
When I start Tails from USB drive "old" with network unplugged 1:28.349
Then the boot device has safe access rights 3.269
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.797
After features/support/hooks.rb:100 0.012
Tags: @product
2:4.833
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:21.320
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 32.241
And I take note of which tps features are available 1.359
Then a Tails persistence partition exists on USB drive "old" 0.914
And I shutdown Tails and wait for the computer to power off 8.394
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.392
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.175
Then Tails is running from USB drive "old" 1.043
And all tps features are active 2.044
When I write some files expected to persist 2.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
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.979
And I take note of which tps features are available 0.608
And I shutdown Tails and wait for the computer to power off 4.453
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.904
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.017
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.216
And I log in to a new session 19.918
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.149
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.100
Then the running Tails is installed on USB drive "to_upgrade" 20.759
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 3.114
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.310
Then all tps features from the old Tails version are active 1.679
And Tails is running from USB drive "to_upgrade" 0.433
And the boot device has safe access rights 3.616
And the expected persistent files created with the old Tails version are present in the filesystem 1.449
And all persistent directories from the old Tails version have safe access rights 2.551
After features/support/hooks.rb:330 1.136
After features/support/hooks.rb:100 0.012
6:37.498
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 with a persistent partition enabled and logged in 13.062
And no SquashFS delta is installed 0.792
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.541
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.137
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.457
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.070
And Tor is ready 25.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.843
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.996
Given I shutdown Tails and wait for the computer to power off 13.533
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.992
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.602
And the file system changes introduced in version 6.2~testoverlayfs are present 0.359
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.307
# 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.328
When the network is plugged 0.080
And Tor is ready 19.547
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.233
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.871
Given I shutdown Tails and wait for the computer to power off 4.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.194
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.957
And the file system changes introduced in version 6.3~testoverlayfs are present 0.690
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.438
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.079
And Tor is ready 18.799
Then the Upgrader considers the system as up-to-date 0.342
# 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.060
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.952
After features/support/hooks.rb:330 0.833
After features/support/hooks.rb:100 0.018
39.722
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 11.764
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 21.310
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.017
After features/support/hooks.rb:330 0.684
After features/support/hooks.rb:100 0.000