Project Number Date
test_Tails_ISO_stable 5404 20 Jan 2025, 14:39

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:9.873 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:22.536
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.662
When I start Tails from USB drive "old" with network unplugged 1:46.354
Then the boot device has safe access rights 3.150
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.143
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:326 3.652
After features/support/hooks.rb:100 0.011
Tags: @product
2:16.556
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:31.530
Then Tails is running from USB drive "old" 0.494
And I create a persistent partition 32.234
And I take note of which tps features are available 1.992
Then a Tails persistence partition exists on USB drive "old" 0.895
And I shutdown Tails and wait for the computer to power off 9.217
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.448
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.910
Then Tails is running from USB drive "old" 0.551
And all tps features are active 2.257
When I write some files expected to persist 1.879
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.311
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.909
And I take note of which tps features are available 0.589
And I shutdown Tails and wait for the computer to power off 4.354
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.073
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.011
Tags: @product
2:26.349
Before features/support/hooks.rb:269 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.167
And I log in to a new session 19.054
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.691
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.399
Then the running Tails is installed on USB drive "to_upgrade" 17.187
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 3.587
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.822
Before features/support/hooks.rb:269 0.005
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.118
Then all tps features from the old Tails version are active 1.771
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.264
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.635
After features/support/hooks.rb:326 0.692
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:55.696
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.550
And no SquashFS delta is installed 0.204
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.555
When the network is plugged 0.082
And Tor is ready 24.557
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.815
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.967
Given I shutdown Tails and wait for the computer to power off 9.083
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.898
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.704
And the file system changes introduced in version 6.2~testoverlayfs are present 0.385
And only the 6.2~testoverlayfs SquashFS delta is installed 0.116
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.476
# 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.473
When the network is plugged 0.096
And Tor is ready 19.731
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.559
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.570
Given I shutdown Tails and wait for the computer to power off 6.229
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.188
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.783
And the file system changes introduced in version 6.3~testoverlayfs are present 0.625
And only the 6.3~testoverlayfs SquashFS delta is installed 0.107
# 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.409
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.667
When the network is plugged 0.097
And Tor is ready 20.590
Then the Upgrader considers the system as up-to-date 0.365
# 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.640
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.206
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
42.462
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.219
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.576
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 23.908
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.482
After features/support/hooks.rb:326 0.966
After features/support/hooks.rb:100 0.000