Project Number Date
test_Tails_ISO_stable 5666 21 May 2025, 09:03

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 19:3.095 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:4.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.078
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.873
When I start Tails from USB drive "old" with network unplugged 1:28.191
Then the boot device has safe access rights 3.114
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 6.976
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.346
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:25.489
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 30.854
And I take note of which tps features are available 1.613
Then a Tails persistence partition exists on USB drive "old" 0.711
And I shutdown Tails and wait for the computer to power off 8.160
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.007
Tags: @product
2:51.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.146
Then Tails is running from USB drive "old" 0.299
And all tps features are active 2.265
When I write some files expected to persist 1.660
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.462
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.454
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.250
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.120
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.511
And I log in to a new session 19.362
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.593
And I plug USB drive "to_upgrade" 2.361
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.241
Then the running Tails is installed on USB drive "to_upgrade" 25.637
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:330 2.190
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.990
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.990
Then all tps features from the old Tails version are active 1.711
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.157
And the expected persistent files created with the old Tails version are present in the filesystem 1.399
And all persistent directories from the old Tails version have safe access rights 2.185
After features/support/hooks.rb:330 1.281
After features/support/hooks.rb:100 0.030
6:35.059
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.879
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.518
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.551
When the network is plugged 0.078
And Tor is ready 19.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.906
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.165
Given I shutdown Tails and wait for the computer to power off 8.696
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.874
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 3.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.378
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.286
When the network is plugged 0.067
And Tor is ready 18.336
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.693
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.741
Given I shutdown Tails and wait for the computer to power off 4.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.531
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.064
And Tor is ready 19.304
Then the Upgrader considers the system as up-to-date 0.318
# 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.878
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.215
After features/support/hooks.rb:330 0.782
After features/support/hooks.rb:100 0.016
38.317
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 11.614
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 19.796
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.368
After features/support/hooks.rb:330 1.541
After features/support/hooks.rb:100 0.000