Project Number Date
test_Tails_ISO_stable 5726 19 Jun 2025, 10:33

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 26:32.957 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:53.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 39.595
When I start Tails from USB drive "old" with network unplugged 2:4.240
Then the boot device has safe access rights 4.520
And Tails is running from USB drive "old" 2.917
And there is no persistence partition on USB drive "old" 0.179
And process "udev-watchdog" is running 0.148
And udev-watchdog is monitoring the correct device 0.631
And I unplug USB drive "old" 0.349
After features/support/hooks.rb:330 4.717
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.885
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.265
And I start Tails from USB drive "old" with network unplugged and I login 1:53.935
Then Tails is running from USB drive "old" 0.967
And I create a persistent partition 42.629
And I take note of which tps features are available 3.039
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 10.185
After features/support/hooks.rb:330 0.933
After features/support/hooks.rb:100 0.065
Tags: @product
3:54.361
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Given a computer 0.703
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:58.978
Then Tails is running from USB drive "old" 0.812
And all tps features are active 4.784
When I write some files expected to persist 2.354
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.398
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.476
And I shutdown Tails and wait for the computer to power off 7.734
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.197
After features/support/hooks.rb:330 0.241
After features/support/hooks.rb:100 0.081
Tags: @product
3:31.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.601
And I log in to a new session 25.259
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.006
And I plug USB drive "to_upgrade" 3.530
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:3.111
Then the running Tails is installed on USB drive "to_upgrade" 34.829
And I unplug USB drive "to_upgrade" 0.409
And I unplug USB drive "__internal" 0.271
After features/support/hooks.rb:330 3.839
After features/support/hooks.rb:100 0.000
Tags: @product
3:13.570
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:58.686
Then all tps features from the old Tails version are active 1.802
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.751
And the expected persistent files created with the old Tails version are present in the filesystem 1.714
And all persistent directories from the old Tails version have safe access rights 7.078
After features/support/hooks.rb:330 1.355
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
8:46.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.037
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.527
And no SquashFS delta is installed 1.714
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.727
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.256
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.999
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.737
When the network is plugged 0.652
And Tor is ready 24.358
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.980
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.747
Given I shutdown Tails and wait for the computer to power off 13.054
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:42.575
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.598
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.263
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.403
# 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.544
When the network is plugged 0.114
And Tor is ready 20.955
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.887
Given I shutdown Tails and wait for the computer to power off 7.148
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.263
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 6.971
And the file system changes introduced in version 6.3~testoverlayfs are present 1.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.172
# 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.424
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.456
When the network is plugged 0.110
And Tor is ready 21.583
Then the Upgrader considers the system as up-to-date 0.326
# 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 22.028
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.789
After features/support/hooks.rb:330 1.046
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
1:21.615
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.373
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.758
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the signing key used by the Upgrader is outdated 0.132
But a current signing key is available on our website 0.000
When the network is plugged 0.232
And Tor is ready 48.228
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.769
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.000