Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 11 22 Apr 2025, 21:20

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 21:7.445 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:12.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 30.728
When I start Tails from USB drive "old" with network unplugged 1:36.387
Then the boot device has safe access rights 2.996
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.687
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.929
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:28.311
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 31.430
And I take note of which tps features are available 2.246
Then a Tails persistence partition exists on USB drive "old" 0.944
And I shutdown Tails and wait for the computer to power off 8.464
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.010
Tags: @product
2:56.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.282
Then Tails is running from USB drive "old" 0.592
And all tps features are active 2.072
When I write some files expected to persist 2.486
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.584
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 6.545
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.201
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.007
Tags: @product
2:36.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.947
And I log in to a new session 21.975
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.926
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.856
Then the running Tails is installed on USB drive "to_upgrade" 24.885
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 0.957
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.113
Then all tps features from the old Tails version are active 1.632
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.459
And the expected persistent files created with the old Tails version are present in the filesystem 1.466
And all persistent directories from the old Tails version have safe access rights 2.423
After features/support/hooks.rb:330 1.380
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:9.251
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 35.355
And no SquashFS delta is installed 0.246
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.168
And Tor is ready 22.042
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.740
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.063
Given I shutdown Tails and wait for the computer to power off 1:16.104
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.825
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.513
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.371
When the network is plugged 0.107
And Tor is ready 19.461
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.708
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.114
Given I shutdown Tails and wait for the computer to power off 4.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.378
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.160
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.095
And Tor is ready 16.604
Then the Upgrader considers the system as up-to-date 0.330
# 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.958
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.473
After features/support/hooks.rb:330 0.726
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.711
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 9.606
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
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.118
And Tor is ready 21.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.354
After features/support/hooks.rb:330 1.960
After features/support/hooks.rb:100 0.000