Project Number Date
test_Tails_ISO_20979-pdfarranger 5 31 May 2025, 02:44

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:37.177 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:19.188
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.083
When I start Tails from USB drive "old" with network unplugged 1:43.620
Then the boot device has safe access rights 3.134
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 3.580
After features/support/hooks.rb:100 0.012
Tags: @product
2:23.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:39.696
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 30.786
And I take note of which tps features are available 2.546
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 8.610
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.012
Tags: @product
3:0.957
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.075
Then Tails is running from USB drive "old" 0.437
And all tps features are active 2.237
When I write some files expected to persist 2.009
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.285
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.479
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.769
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.558
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.479
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 without a persistent partition and stopped at Tails Greeter's login screen 10.345
And I log in to a new session 19.578
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.497
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.376
Then the running Tails is installed on USB drive "to_upgrade" 24.744
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.250
After features/support/hooks.rb:330 2.075
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.584
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.656
Then all tps features from the old Tails version are active 1.540
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.640
And the expected persistent files created with the old Tails version are present in the filesystem 1.553
And all persistent directories from the old Tails version have safe access rights 2.616
After features/support/hooks.rb:330 1.515
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:23.369
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 12.313
And no SquashFS delta is installed 0.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.685
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.162
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.476
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.067
And Tor is ready 22.992
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.760
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.950
Given I shutdown Tails and wait for the computer to power off 1:18.776
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.178
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.224
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.403
# 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.255
When the network is plugged 0.063
And Tor is ready 17.855
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.978
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.874
Given I shutdown Tails and wait for the computer to power off 4.483
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.769
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.230
And the file system changes introduced in version 6.3~testoverlayfs are present 0.562
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.067
And Tor is ready 47.196
Then the Upgrader considers the system as up-to-date 0.303
# 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.337
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.543
After features/support/hooks.rb:330 0.739
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.449
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.623
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.091
And the signing key used by the Upgrader is outdated 0.115
But a current signing key is available on our website 0.000
When the network is plugged 0.117
And Tor is ready 21.130
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.924
After features/support/hooks.rb:330 0.835
After features/support/hooks.rb:100 0.000