Project Number Date
test_Tails_ISO_codespell 5 18 Jun 2025, 16:28

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 22:41.285 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:25.276
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 38.670
When I start Tails from USB drive "old" with network unplugged 1:40.851
Then the boot device has safe access rights 3.245
And Tails is running from USB drive "old" 0.535
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 4.842
After features/support/hooks.rb:100 0.016
Tags: @product
2:40.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.269
And I start Tails from USB drive "old" with network unplugged and I login 1:49.394
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 38.197
And I take note of which tps features are available 2.119
Then a Tails persistence partition exists on USB drive "old" 0.751
And I shutdown Tails and wait for the computer to power off 8.999
After features/support/hooks.rb:330 1.288
After features/support/hooks.rb:100 0.036
Tags: @product
3:32.397
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.097
Given a computer 0.959
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:45.577
Then Tails is running from USB drive "old" 1.237
And all tps features are active 2.162
When I write some files expected to persist 1.742
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.328
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.974
And I take note of which tps features are available 0.449
And I shutdown Tails and wait for the computer to power off 8.025
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.507
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.816
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 without a persistent partition and stopped at Tails Greeter's login screen 13.034
And I log in to a new session 22.625
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.615
And I plug USB drive "to_upgrade" 2.459
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.301
Then the running Tails is installed on USB drive "to_upgrade" 32.335
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 2.160
After features/support/hooks.rb:100 0.000
Tags: @product
2:44.006
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.360
Then all tps features from the old Tails version are active 3.049
And Tails is running from USB drive "to_upgrade" 0.458
And the boot device has safe access rights 4.176
And the expected persistent files created with the old Tails version are present in the filesystem 1.533
And all persistent directories from the old Tails version have safe access rights 3.252
After features/support/hooks.rb:330 1.494
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:36.614
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 17.988
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.587
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.505
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.838
When the network is plugged 0.066
And Tor is ready 26.051
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.718
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.687
Given I shutdown Tails and wait for the computer to power off 11.391
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.996
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.656
And the file system changes introduced in version 6.2~testoverlayfs are present 0.615
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.628
# 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.466
When the network is plugged 0.092
And Tor is ready 21.609
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.429
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.058
Given I shutdown Tails and wait for the computer to power off 4.527
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.676
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.503
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.356
When the network is plugged 0.064
And Tor is ready 20.878
Then the Upgrader considers the system as up-to-date 0.297
# 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.871
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.863
After features/support/hooks.rb:330 1.139
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
47.110
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 13.405
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 21.713
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.185
After features/support/hooks.rb:330 1.612
After features/support/hooks.rb:100 0.000