Project Number Date
test_Tails_ISO_devel 3828 21 May 2025, 22:52

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:12.634 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:9.507
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.585
When I start Tails from USB drive "old" with network unplugged 1:32.438
Then the boot device has safe access rights 3.183
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 3.783
After features/support/hooks.rb:100 0.011
Tags: @product
2:22.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:35.524
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 35.704
And I take note of which tps features are available 1.752
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 8.596
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.056
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.657
Then Tails is running from USB drive "old" 0.454
And all tps features are active 1.865
When I write some files expected to persist 1.903
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.612
And all persistent directories from the old Tails version have safe access rights 2.862
And I take note of which tps features are available 0.382
And I shutdown Tails and wait for the computer to power off 4.505
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.399
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.012
Tags: @product
2:37.722
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.979
And I log in to a new session 18.786
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.284
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.166
Then the running Tails is installed on USB drive "to_upgrade" 25.636
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 7.160
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.609
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.233
Then all tps features from the old Tails version are active 1.560
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.286
And the expected persistent files created with the old Tails version are present in the filesystem 1.640
And all persistent directories from the old Tails version have safe access rights 2.328
After features/support/hooks.rb:330 1.092
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:4.219
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.571
And no SquashFS delta is installed 0.354
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.423
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.089
And Tor is ready 20.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.466
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.594
Given I shutdown Tails and wait for the computer to power off 8.581
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.647
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.031
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.270
When the network is plugged 0.068
And Tor is ready 16.798
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.170
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.955
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.472
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 5.979
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.412
And Tor is ready 46.378
Then the Upgrader considers the system as up-to-date 0.301
# 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.567
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.315
After features/support/hooks.rb:330 0.727
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.611
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 with a persistent partition enabled and logged in 10.739
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.624
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 21.194
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.814
After features/support/hooks.rb:330 1.173
After features/support/hooks.rb:100 0.000