Project Number Date
test_Tails_ISO_stable 5476 21 Feb 2025, 15:49

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 19:20.278 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:2.402
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 29.716
When I start Tails from USB drive "old" with network unplugged 1:27.198
Then the boot device has safe access rights 3.049
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.124
And udev-watchdog is monitoring the correct device 0.376
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 7.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.775
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:22.974
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 33.471
And I take note of which tps features are available 1.360
Then a Tails persistence partition exists on USB drive "old" 0.862
And I shutdown Tails and wait for the computer to power off 8.586
After features/support/hooks.rb:330 0.239
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.786
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.461
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.177
When I write some files expected to persist 1.708
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.635
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.347
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.814
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.577
And I log in to a new session 19.101
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.692
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.245
Then the running Tails is installed on USB drive "to_upgrade" 23.549
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 2.349
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.885
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.048
Then all tps features from the old Tails version are active 1.676
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.243
And the expected persistent files created with the old Tails version are present in the filesystem 1.805
And all persistent directories from the old Tails version have safe access rights 2.596
After features/support/hooks.rb:330 1.247
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
6:50.763
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 11.422
And no SquashFS delta is installed 0.231
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.084
And Tor is ready 51.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.599
Given I shutdown Tails and wait for the computer to power off 8.894
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.699
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.429
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.474
# 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.361
When the network is plugged 0.069
And Tor is ready 18.598
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.858
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.226
Given I shutdown Tails and wait for the computer to power off 4.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.024
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.024
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.337
When the network is plugged 0.102
And Tor is ready 18.237
Then the Upgrader considers the system as up-to-date 0.295
# 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.297
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.014
After features/support/hooks.rb:330 0.716
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
36.633
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 10.260
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.443
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 19.481
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.225
After features/support/hooks.rb:330 0.945
After features/support/hooks.rb:100 0.000