Project Number Date
test_Tails_ISO_stable 5503 08 Mar 2025, 12:43

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 18:51.567 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
1:59.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.507
When I start Tails from USB drive "old" with network unplugged 1:24.385
Then the boot device has safe access rights 2.854
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 3.527
After features/support/hooks.rb:100 0.028
Tags: @product
2:5.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:21.222
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 32.870
And I take note of which tps features are available 1.402
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.613
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.012
Tags: @product
2:55.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.938
Then Tails is running from USB drive "old" 0.424
And all tps features are active 2.270
When I write some files expected to persist 1.838
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.492
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.439
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.216
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.666
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 11.059
And I log in to a new session 19.096
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.535
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.218
Then the running Tails is installed on USB drive "to_upgrade" 24.798
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.299
After features/support/hooks.rb:330 3.683
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.889
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.242
Then all tps features from the old Tails version are active 1.825
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.431
And the expected persistent files created with the old Tails version are present in the filesystem 1.432
And all persistent directories from the old Tails version have safe access rights 2.415
After features/support/hooks.rb:330 1.085
After features/support/hooks.rb:100 0.032
6:22.973
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.488
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.079
And Tor is ready 22.452
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.159
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.061
Given I shutdown Tails and wait for the computer to power off 8.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.190
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.391
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.282
# 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.304
When the network is plugged 0.074
And Tor is ready 19.713
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.275
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.024
Given I shutdown Tails and wait for the computer to power off 4.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.388
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.290
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.081
And Tor is ready 19.970
Then the Upgrader considers the system as up-to-date 0.323
# 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.326
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.086
After features/support/hooks.rb:330 0.760
After features/support/hooks.rb:100 0.019
37.464
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.635
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 19.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.341
After features/support/hooks.rb:330 1.081
After features/support/hooks.rb:100 0.000