Project Number Date
test_Tails_ISO_devel 3762 02 Apr 2025, 14:02

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:4.828 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:32.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.987
When I start Tails from USB drive "old" with network unplugged 1:55.562
Then the boot device has safe access rights 3.337
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.367
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:330 3.811
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:30.383
Then Tails is running from USB drive "old" 0.432
And I create a persistent partition 33.284
And I take note of which tps features are available 2.082
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 9.107
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.450
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.381
Then Tails is running from USB drive "old" 0.422
And all tps features are active 2.344
When I write some files expected to persist 1.751
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.445
And I take note of which tps features are available 0.396
And I shutdown Tails and wait for the computer to power off 6.239
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.531
After features/support/hooks.rb:330 0.122
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.404
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 12.243
And I log in to a new session 24.010
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.141
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.053
Then the running Tails is installed on USB drive "to_upgrade" 29.037
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:330 6.801
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.615
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.323
Then all tps features from the old Tails version are active 2.066
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.451
And the expected persistent files created with the old Tails version are present in the filesystem 1.508
And all persistent directories from the old Tails version have safe access rights 2.704
After features/support/hooks.rb:330 1.488
After features/support/hooks.rb:100 0.010
8:9.637
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 12.974
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.593
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.476
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.578
When the network is plugged 0.090
And Tor is ready 23.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.153
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.376
Given I shutdown Tails and wait for the computer to power off 1:31.205
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.460
Then Tails is running version 6.2~testoverlayfs 0.043
And all tps features are active 2.497
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
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.302
# 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.078
And Tor is ready 18.478
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.045
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.829
Given I shutdown Tails and wait for the computer to power off 4.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.276
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.937
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.284
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.066
And Tor is ready 16.917
Then the Upgrader considers the system as up-to-date 0.302
# 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 14.466
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.556
After features/support/hooks.rb:330 0.800
After features/support/hooks.rb:100 0.062
40.015
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.656
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.858
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.897
After features/support/hooks.rb:330 1.118
After features/support/hooks.rb:100 0.000