Project Number Date
test_Tails_ISO_devel 3718 04 Mar 2025, 09:18

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 18:22.032 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
1:58.042
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.491
When I start Tails from USB drive "old" with network unplugged 1:23.211
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 3.550
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.766
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:19.934
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 32.848
And I take note of which tps features are available 1.346
Then a Tails persistence partition exists on USB drive "old" 0.903
And I shutdown Tails and wait for the computer to power off 8.248
After features/support/hooks.rb:330 0.222
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.188
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.923
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.782
When I write some files expected to persist 1.612
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.849
And I take note of which tps features are available 0.398
And I shutdown Tails and wait for the computer to power off 4.357
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.170
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.623
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 without a persistent partition and stopped at Tails Greeter's login screen 11.291
And I log in to a new session 19.684
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.992
And I plug USB drive "to_upgrade" 2.511
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.350
Then the running Tails is installed on USB drive "to_upgrade" 20.383
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 2.301
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.238
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.309
Then all tps features from the old Tails version are active 1.430
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.193
And the expected persistent files created with the old Tails version are present in the filesystem 1.547
And all persistent directories from the old Tails version have safe access rights 2.265
After features/support/hooks.rb:330 1.053
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:24.686
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 12.240
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.062
And Tor is ready 18.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.468
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.460
Given I shutdown Tails and wait for the computer to power off 8.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.403
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.917
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.303
When the network is plugged 0.062
And Tor is ready 18.963
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.461
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.850
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.083
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.975
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.376
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.071
And Tor is ready 17.852
Then the Upgrader considers the system as up-to-date 10.748
# 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.002
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.882
After features/support/hooks.rb:330 0.770
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.485
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 10.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
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.076
And Tor is ready 18.257
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.398
After features/support/hooks.rb:330 1.550
After features/support/hooks.rb:100 0.000