Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 8 19 Apr 2025, 21:17

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:16.580 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:4.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.625
When I start Tails from USB drive "old" with network unplugged 1:27.295
Then the boot device has safe access rights 2.966
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.536
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.190
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:25.953
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 30.637
And I take note of which tps features are available 1.835
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 8.408
After features/support/hooks.rb:330 0.228
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.358
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.552
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.046
When I write some files expected to persist 2.072
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.487
And I take note of which tps features are available 0.588
And I shutdown Tails and wait for the computer to power off 6.608
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.748
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.244
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 without a persistent partition and stopped at Tails Greeter's login screen 10.857
And I log in to a new session 18.617
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.480
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.317
Then the running Tails is installed on USB drive "to_upgrade" 20.140
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:330 3.362
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.257
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.040
Then all tps features from the old Tails version are active 1.903
And Tails is running from USB drive "to_upgrade" 0.430
And the boot device has safe access rights 3.199
And the expected persistent files created with the old Tails version are present in the filesystem 1.518
And all persistent directories from the old Tails version have safe access rights 2.505
After features/support/hooks.rb:330 1.380
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:42.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.029
And no SquashFS delta is installed 0.178
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
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.351
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.561
When the network is plugged 0.064
And Tor is ready 22.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.956
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.506
Given I shutdown Tails and wait for the computer to power off 11.246
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.940
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.258
And the file system changes introduced in version 6.2~testoverlayfs are present 0.368
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.323
When the network is plugged 0.069
And Tor is ready 22.149
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.235
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.083
Given I shutdown Tails and wait for the computer to power off 4.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.966
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.166
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.072
And Tor is ready 19.817
Then the Upgrader considers the system as up-to-date 0.319
# 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.498
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.744
After features/support/hooks.rb:330 0.753
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.530
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.308
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
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.110
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 19.986
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.582
After features/support/hooks.rb:330 0.858
After features/support/hooks.rb:100 0.000