Project Number Date
test_Tails_ISO_stable 4733 21 Mar 2024, 12:10

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 16:51.978 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:34.429
Before features/support/hooks.rb:245 0.004
Given a computer 0.156
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 20.092
When I start Tails from USB drive "old" with network unplugged 1:9.394
Then the boot device has safe access rights 2.763
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:291 3.719
After features/support/hooks.rb:75 0.010
Tags: @product
1:54.598
Before features/support/hooks.rb:245 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:14.060
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 32.035
And I take note of which tps features are available 1.256
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 6.022
After features/support/hooks.rb:291 0.169
After features/support/hooks.rb:75 0.010
Tags: @product
2:28.685
Before features/support/hooks.rb:245 0.006
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.294
Then Tails is running from USB drive "old" 0.339
And all tps features are active 1.529
When I write some files expected to persist 1.419
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.361
And I take note of which tps features are available 0.324
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.590
After features/support/hooks.rb:291 0.135
After features/support/hooks.rb:75 0.010
Tags: @product
2:20.629
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 9.758
And I log in to a new session 16.563
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.592
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.107
Then the running Tails is installed on USB drive "to_upgrade" 13.809
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.172
After features/support/hooks.rb:291 2.570
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.150
Before features/support/hooks.rb:245 0.005
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.144
Then all tps features from the old Tails version are active 1.565
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 2.991
And the expected persistent files created with the old Tails version are present in the filesystem 1.440
And all persistent directories from the old Tails version have safe access rights 2.505
After features/support/hooks.rb:291 0.691
After features/support/hooks.rb:75 0.010
6:0.273
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 12.231
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.062
And Tor is ready 17.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.318
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.784
Given I shutdown Tails and wait for the computer to power off 6.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.360
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.857
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.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.301
When the network is plugged 0.030
And Tor is ready 18.027
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.331
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.015
Given I shutdown Tails and wait for the computer to power off 4.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.939
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.635
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.040
And Tor is ready 17.626
Then the Upgrader considers the system as up-to-date 0.237
# 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.475
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.900
After features/support/hooks.rb:291 0.964
After features/support/hooks.rb:75 0.022
32.211
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.763
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.425
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 13.769
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.859
After features/support/hooks.rb:291 1.156
After features/support/hooks.rb:75 0.000