Project Number Date
test_Tails_ISO_devel 3813 15 May 2025, 12:54

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:22.464 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:30.804
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.613
When I start Tails from USB drive "old" with network unplugged 1:53.659
Then the boot device has safe access rights 3.891
And Tails is running from USB drive "old" 0.485
And there is no persistence partition on USB drive "old" 0.094
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.277
After features/support/hooks.rb:330 7.103
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.042
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:30.963
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 30.984
And I take note of which tps features are available 2.559
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 9.156
After features/support/hooks.rb:330 0.205
After features/support/hooks.rb:100 0.010
Tags: @product
3:8.939
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.776
Then Tails is running from USB drive "old" 0.354
And all tps features are active 2.229
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.280
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.700
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 4.580
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.119
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.246
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.950
And I log in to a new session 23.147
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.927
And I plug USB drive "to_upgrade" 2.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.134
Then the running Tails is installed on USB drive "to_upgrade" 25.154
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 1.934
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.198
Then all tps features from the old Tails version are active 1.916
And Tails is running from USB drive "to_upgrade" 0.424
And the boot device has safe access rights 3.782
And the expected persistent files created with the old Tails version are present in the filesystem 1.543
And all persistent directories from the old Tails version have safe access rights 2.669
After features/support/hooks.rb:330 1.687
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:38.948
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 26.708
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.139
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.713
When the network is plugged 0.063
And Tor is ready 20.883
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.549
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.473
Given I shutdown Tails and wait for the computer to power off 8.530
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.552
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.222
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.412
# 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.258
When the network is plugged 0.057
And Tor is ready 17.423
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.957
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.738
Given I shutdown Tails and wait for the computer to power off 4.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.681
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.911
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.084
And Tor is ready 15.855
Then the Upgrader considers the system as up-to-date 0.366
# 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.273
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.447
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.763
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.245
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 21.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.597
After features/support/hooks.rb:330 0.959
After features/support/hooks.rb:100 0.000