Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 7 18 Apr 2025, 21:28

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:15.104 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:28.498
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.667
When I start Tails from USB drive "old" with network unplugged 1:50.299
Then the boot device has safe access rights 3.154
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.127
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.727
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.659
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:38.804
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 32.981
And I take note of which tps features are available 2.012
Then a Tails persistence partition exists on USB drive "old" 1.032
And I shutdown Tails and wait for the computer to power off 8.252
After features/support/hooks.rb:330 0.211
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.157
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.252
Then Tails is running from USB drive "old" 0.380
And all tps features are active 2.351
When I write some files expected to persist 1.757
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.753
And I take note of which tps features are available 0.876
And I shutdown Tails and wait for the computer to power off 4.549
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.375
After features/support/hooks.rb:330 0.107
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.615
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 11.772
And I log in to a new session 18.984
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.819
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.860
Then the running Tails is installed on USB drive "to_upgrade" 23.296
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:330 2.032
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.195
Then all tps features from the old Tails version are active 1.820
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.266
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 2.576
After features/support/hooks.rb:330 1.528
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:51.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.370
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.579
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.645
When the network is plugged 0.087
And Tor is ready 23.906
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.225
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.859
Given I shutdown Tails and wait for the computer to power off 8.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.133
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.557
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.104
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.262
When the network is plugged 0.088
And Tor is ready 18.291
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.697
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.399
Given I shutdown Tails and wait for the computer to power off 4.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.920
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.284
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.068
And Tor is ready 19.993
Then the Upgrader considers the system as up-to-date 0.327
# 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 16.201
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.944
After features/support/hooks.rb:330 0.702
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.232
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.615
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 20.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.708
After features/support/hooks.rb:330 1.123
After features/support/hooks.rb:100 0.000