Project Number Date
test_Tails_ISO_stable 5588 22 Apr 2025, 14:36

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:49.376 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:31.377
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 36.743
When I start Tails from USB drive "old" with network unplugged 1:49.098
Then the boot device has safe access rights 3.155
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:330 3.738
After features/support/hooks.rb:100 0.025
Tags: @product
2:13.137
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:29.072
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 31.744
And I take note of which tps features are available 2.465
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.483
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.010
Tags: @product
3:7.584
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.471
Then Tails is running from USB drive "old" 0.962
And all tps features are active 5.501
When I write some files expected to persist 2.910
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.431
And I take note of which tps features are available 1.170
And I shutdown Tails and wait for the computer to power off 4.522
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.739
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.011
Tags: @product
3:2.620
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 without a persistent partition and stopped at Tails Greeter's login screen 31.476
And I log in to a new session 19.411
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.708
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.423
Then the running Tails is installed on USB drive "to_upgrade" 25.780
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 0.980
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.254
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.683
Then all tps features from the old Tails version are active 1.548
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.299
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.542
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.013
6:54.601
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 12.598
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.597
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.666
When the network is plugged 0.088
And Tor is ready 22.777
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.571
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.691
Given I shutdown Tails and wait for the computer to power off 8.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.556
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.328
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.351
When the network is plugged 0.088
And Tor is ready 19.700
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.492
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.657
Given I shutdown Tails and wait for the computer to power off 4.436
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.516
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.573
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.401
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.349
When the network is plugged 0.090
And Tor is ready 21.812
Then the Upgrader considers the system as up-to-date 0.321
# 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 17.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.797
After features/support/hooks.rb:330 0.716
After features/support/hooks.rb:100 0.019
40.880
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.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.106
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 20.089
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.944
After features/support/hooks.rb:330 1.548
After features/support/hooks.rb:100 0.000