Project Number Date
test_Tails_ISO_stable 4715 13 Mar 2024, 15:32

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 17:6.319 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
1:38.884
Before features/support/hooks.rb:245 0.004
Given a computer 0.154
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 19.364
When I start Tails from USB drive "old" with network unplugged 1:14.286
Then the boot device has safe access rights 2.993
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:291 3.576
After features/support/hooks.rb:75 0.011
Tags: @product
2:6.278
Before features/support/hooks.rb:245 0.007
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:14.808
Then Tails is running from USB drive "old" 0.296
And I create a persistent partition 40.359
And I take note of which tps features are available 1.759
Then a Tails persistence partition exists on USB drive "old" 0.714
And I shutdown Tails and wait for the computer to power off 8.169
After features/support/hooks.rb:291 0.224
After features/support/hooks.rb:75 0.017
Tags: @product
2:26.775
Before features/support/hooks.rb:245 0.007
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.682
Then Tails is running from USB drive "old" 0.318
And all tps features are active 2.069
When I write some files expected to persist 1.538
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.455
And I take note of which tps features are available 0.381
And I shutdown Tails and wait for the computer to power off 4.017
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.596
After features/support/hooks.rb:291 0.091
After features/support/hooks.rb:75 0.009
Tags: @product
2:27.457
Before features/support/hooks.rb:245 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.230
And I log in to a new session 17.214
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.564
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.089
Then the running Tails is installed on USB drive "to_upgrade" 13.541
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:291 6.585
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.505
Before features/support/hooks.rb:245 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.908
Then all tps features from the old Tails version are active 1.363
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.958
And the expected persistent files created with the old Tails version are present in the filesystem 1.364
And all persistent directories from the old Tails version have safe access rights 2.419
After features/support/hooks.rb:291 0.702
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:0.581
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.299
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.034
And Tor is ready 19.853
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.978
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.124
Given I shutdown Tails and wait for the computer to power off 6.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.040
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.772
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.284
# 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.249
When the network is plugged 0.029
And Tor is ready 17.851
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.256
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.999
Given I shutdown Tails and wait for the computer to power off 5.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.780
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.192
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.284
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.085
And Tor is ready 15.165
Then the Upgrader considers the system as up-to-date 0.298
# 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 13.494
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.056
After features/support/hooks.rb:291 0.736
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
30.836
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.921
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.485
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 14.747
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.265
After features/support/hooks.rb:291 0.847
After features/support/hooks.rb:75 0.000