Project Number Date
test_Tails_ISO_stable 4745 26 Mar 2024, 18:24

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:24.436 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:43.776
Before features/support/hooks.rb:245 0.008
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 21.451
When I start Tails from USB drive "old" with network unplugged 1:16.796
Then the boot device has safe access rights 3.167
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.379
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 3.812
After features/support/hooks.rb:75 0.011
Tags: @product
1:57.804
Before features/support/hooks.rb:245 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:16.110
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 32.528
And I take note of which tps features are available 1.474
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 6.362
After features/support/hooks.rb:291 0.242
After features/support/hooks.rb:75 0.012
Tags: @product
2:32.212
Before features/support/hooks.rb:245 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.000
Then Tails is running from USB drive "old" 0.376
And all tps features are active 2.029
When I write some files expected to persist 1.622
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.532
And all persistent directories from the old Tails version have safe access rights 2.559
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.365
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.846
After features/support/hooks.rb:291 0.162
After features/support/hooks.rb:75 0.018
Tags: @product
2:22.174
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.819
And I log in to a new session 15.541
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.516
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.201
Then the running Tails is installed on USB drive "to_upgrade" 14.262
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 6.622
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.340
Before features/support/hooks.rb:245 0.005
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.083
Then all tps features from the old Tails version are active 1.472
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.125
And the expected persistent files created with the old Tails version are present in the filesystem 1.610
And all persistent directories from the old Tails version have safe access rights 2.500
After features/support/hooks.rb:291 0.719
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:13.300
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.861
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.525
When the network is plugged 0.034
And Tor is ready 17.486
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.297
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.158
Given I shutdown Tails and wait for the computer to power off 9.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.191
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.164
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.320
When the network is plugged 0.036
And Tor is ready 14.578
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.693
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.729
Given I shutdown Tails and wait for the computer to power off 4.408
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.244
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.963
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.043
And Tor is ready 19.320
Then the Upgrader considers the system as up-to-date 0.243
# 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.144
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.727
After features/support/hooks.rb:291 0.744
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
34.826
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 10.610
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
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.479
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 16.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.824
After features/support/hooks.rb:291 0.670
After features/support/hooks.rb:75 0.000