Project Number Date
test_Tails_ISO_stable 5598 24 Apr 2025, 20:21

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:38.326 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:57.575
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.494
When I start Tails from USB drive "old" with network unplugged 1:21.330
Then the boot device has safe access rights 3.441
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 3.580
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.776
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login 1:27.325
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 30.612
And I take note of which tps features are available 3.709
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.710
After features/support/hooks.rb:330 0.210
After features/support/hooks.rb:100 0.008
Tags: @product
3:3.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.035
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.399
Then Tails is running from USB drive "old" 0.406
And all tps features are active 2.458
When I write some files expected to persist 2.072
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.374
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 2.810
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 4.623
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.403
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.702
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.190
And I log in to a new session 20.263
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.468
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.258
Then the running Tails is installed on USB drive "to_upgrade" 23.639
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 0.979
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.255
Then all tps features from the old Tails version are active 1.544
And Tails is running from USB drive "to_upgrade" 0.496
And the boot device has safe access rights 3.730
And the expected persistent files created with the old Tails version are present in the filesystem 1.523
And all persistent directories from the old Tails version have safe access rights 2.681
After features/support/hooks.rb:330 1.113
After features/support/hooks.rb:100 0.009
7:42.660
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.994
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.454
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.199
And Tor is ready 24.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.595
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.135
Given I shutdown Tails and wait for the computer to power off 8.787
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.789
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.596
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.312
When the network is plugged 0.065
And Tor is ready 19.659
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.783
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.838
Given I shutdown Tails and wait for the computer to power off 4.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.046
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 3.974
And the file system changes introduced in version 6.3~testoverlayfs are present 0.547
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.342
When the network is plugged 0.385
And Tor is ready 47.472
Then the Upgrader considers the system as up-to-date 0.331
# 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.706
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.742
After features/support/hooks.rb:330 0.773
After features/support/hooks.rb:100 0.017
42.383
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 12.320
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.949
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 21.919
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.978
After features/support/hooks.rb:330 0.865
After features/support/hooks.rb:100 0.000