Project Number Date
test_Tails_ISO_stable 5423 28 Jan 2025, 00:22

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:33.598 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.301
Before features/support/hooks.rb:269 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.309
When I start Tails from USB drive "old" with network unplugged 1:21.581
Then the boot device has safe access rights 3.147
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.984
Before features/support/hooks.rb:269 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:23.363
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 32.422
And I take note of which tps features are available 1.352
Then a Tails persistence partition exists on USB drive "old" 0.917
And I shutdown Tails and wait for the computer to power off 8.412
After features/support/hooks.rb:326 0.213
After features/support/hooks.rb:100 0.040
Tags: @product
2:50.448
Before features/support/hooks.rb:269 0.010
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.299
Then Tails is running from USB drive "old" 0.956
And all tps features are active 1.817
When I write some files expected to persist 1.611
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 4.484
And I take note of which tps features are available 0.391
And I shutdown Tails and wait for the computer to power off 4.701
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.355
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.837
Before features/support/hooks.rb:269 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 10.559
And I log in to a new session 17.398
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.034
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.713
Then the running Tails is installed on USB drive "to_upgrade" 20.188
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 2.207
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.764
Before features/support/hooks.rb:269 0.005
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.536
Then all tps features from the old Tails version are active 1.557
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.085
And the expected persistent files created with the old Tails version are present in the filesystem 1.452
And all persistent directories from the old Tails version have safe access rights 2.642
After features/support/hooks.rb:326 0.622
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:21.508
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.300
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.738
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
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.578
When the network is plugged 0.146
And Tor is ready 21.284
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.579
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.996
Given I shutdown Tails and wait for the computer to power off 8.936
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.205
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.087
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.291
When the network is plugged 0.075
And Tor is ready 16.092
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.647
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.733
Given I shutdown Tails and wait for the computer to power off 4.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.668
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.968
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.069
And Tor is ready 17.331
Then the Upgrader considers the system as up-to-date 0.325
# 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 14.834
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.968
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.753
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.910
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 19.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.276
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.000