Project Number Date
test_Tails_ISO_devel 3878 21 Jun 2025, 20: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 23:56.642 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:38.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 34.524
When I start Tails from USB drive "old" with network unplugged 1:53.815
Then the boot device has safe access rights 6.753
And Tails is running from USB drive "old" 0.491
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.462
And I unplug USB drive "old" 0.573
After features/support/hooks.rb:330 3.830
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:43.223
Then Tails is running from USB drive "old" 0.464
And I create a persistent partition 40.180
And I take note of which tps features are available 2.499
Then a Tails persistence partition exists on USB drive "old" 0.911
And I shutdown Tails and wait for the computer to power off 9.328
After features/support/hooks.rb:330 0.284
After features/support/hooks.rb:100 0.011
Tags: @product
3:36.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:44.172
Then Tails is running from USB drive "old" 0.476
And all tps features are active 2.180
When I write some files expected to persist 2.373
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 5.614
And I take note of which tps features are available 0.693
And I shutdown Tails and wait for the computer to power off 6.944
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 33.240
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.012
Tags: @product
2:59.651
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.949
And I log in to a new session 28.416
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.601
And I plug USB drive "to_upgrade" 2.515
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.132
Then the running Tails is installed on USB drive "to_upgrade" 32.599
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 3.520
After features/support/hooks.rb:100 0.000
Tags: @product
2:49.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.248
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:37.206
Then all tps features from the old Tails version are active 2.291
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 4.088
And the expected persistent files created with the old Tails version are present in the filesystem 1.592
And all persistent directories from the old Tails version have safe access rights 3.547
After features/support/hooks.rb:330 1.546
After features/support/hooks.rb:100 0.020
8:30.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.558
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.637
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.475
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.553
When the network is plugged 0.070
And Tor is ready 28.677
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.510
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.987
Given I shutdown Tails and wait for the computer to power off 15.106
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:42.486
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 3.120
And the file system changes introduced in version 6.2~testoverlayfs are present 0.477
And only the 6.2~testoverlayfs SquashFS delta is installed 0.115
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.392
# 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.383
When the network is plugged 0.076
And Tor is ready 21.108
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.490
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.204
Given I shutdown Tails and wait for the computer to power off 7.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.876
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 5.395
And the file system changes introduced in version 6.3~testoverlayfs are present 1.540
And only the 6.3~testoverlayfs SquashFS delta is installed 0.216
# 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.436
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.788
When the network is plugged 0.197
And Tor is ready 21.042
Then the Upgrader considers the system as up-to-date 0.444
# 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 19.331
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.887
After features/support/hooks.rb:330 0.819
After features/support/hooks.rb:100 0.019
45.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.266
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.844
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.165
And the signing key used by the Upgrader is outdated 0.138
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 22.570
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.377
After features/support/hooks.rb:330 1.687
After features/support/hooks.rb:100 0.000