Project Number Date
test_Tails_ISO_stable 5572 14 Apr 2025, 13:46

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:12.519 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:12.645
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 38.203
When I start Tails from USB drive "old" with network unplugged 1:28.606
Then the boot device has safe access rights 3.325
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.291
After features/support/hooks.rb:330 3.821
After features/support/hooks.rb:100 0.017
Tags: @product
2:10.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:27.169
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 31.399
And I take note of which tps features are available 1.989
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.944
After features/support/hooks.rb:330 0.201
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.033
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.318
When I write some files expected to persist 1.796
# 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.437
And all persistent directories from the old Tails version have safe access rights 2.668
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 4.427
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.831
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.007
Tags: @product
2:29.401
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.975
And I log in to a new session 18.631
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.780
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.183
Then the running Tails is installed on USB drive "to_upgrade" 21.918
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 2.538
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.813
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.271
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.490
Then all tps features from the old Tails version are active 1.675
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.333
And the expected persistent files created with the old Tails version are present in the filesystem 2.330
And all persistent directories from the old Tails version have safe access rights 3.346
After features/support/hooks.rb:330 1.136
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:19.146
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 14.471
And no SquashFS delta is installed 0.415
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.899
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.435
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.158
And Tor is ready 24.779
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.103
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.806
Given I shutdown Tails and wait for the computer to power off 10.942
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.095
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.112
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.458
# 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.344
When the network is plugged 0.073
And Tor is ready 46.805
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.774
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.456
Given I shutdown Tails and wait for the computer to power off 4.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.691
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.013
And the file system changes introduced in version 6.3~testoverlayfs are present 0.673
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.392
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.366
When the network is plugged 0.146
And Tor is ready 18.934
Then the Upgrader considers the system as up-to-date 0.315
# 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.807
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.028
After features/support/hooks.rb:330 0.666
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
41.840
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.310
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 20.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.057
After features/support/hooks.rb:330 0.723
After features/support/hooks.rb:100 0.000