Project Number Date
test_Tails_ISO_stable 5199 19 Oct 2024, 12:36

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:13.326 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:16.430
Before features/support/hooks.rb:269 0.011
Given a computer 0.391
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 30.456
When I start Tails from USB drive "old" with network unplugged 1:40.247
Then the boot device has safe access rights 3.240
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.582
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.971
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:24.037
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 31.585
And I take note of which tps features are available 1.692
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.268
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.007
Tags: @product
3:1.872
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.544
Then Tails is running from USB drive "old" 0.520
And all tps features are active 2.016
When I write some files expected to persist 1.715
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.496
And all persistent directories from the old Tails version have safe access rights 2.723
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.293
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.644
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.467
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.510
And I log in to a new session 26.752
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.823
And I plug USB drive "to_upgrade" 2.661
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.669
Then the running Tails is installed on USB drive "to_upgrade" 17.661
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 2.813
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.345
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.507
Then all tps features from the old Tails version are active 1.689
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.200
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.909
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:25.114
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.979
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
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.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.066
And Tor is ready 21.661
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.637
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.453
Given I shutdown Tails and wait for the computer to power off 8.640
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.603
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.240
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.272
When the network is plugged 0.088
And Tor is ready 20.194
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.088
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.321
Given I shutdown Tails and wait for the computer to power off 4.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.954
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.692
And only the 6.3~testoverlayfs SquashFS delta is installed 0.162
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.551
When the network is plugged 0.103
And Tor is ready 19.311
Then the Upgrader considers the system as up-to-date 10.862
# 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.485
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.819
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.124
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.970
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.842
But a current signing key is available on our website 0.000
When the network is plugged 0.148
And Tor is ready 17.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.098
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.000