Project Number Date
test_Tails_ISO_stable 5485 02 Mar 2025, 12:33

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:31.579 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.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.605
When I start Tails from USB drive "old" with network unplugged 1:27.824
Then the boot device has safe access rights 3.000
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 7.027
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:21.330
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 31.549
And I take note of which tps features are available 1.461
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.559
After features/support/hooks.rb:330 0.223
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.187
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.665
Then Tails is running from USB drive "old" 0.300
And all tps features are active 2.341
When I write some files expected to persist 1.774
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.449
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.740
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.621
After features/support/hooks.rb:330 0.089
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.961
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.148
And I log in to a new session 21.425
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.650
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.540
Then the running Tails is installed on USB drive "to_upgrade" 23.302
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 1.792
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.963
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 "to_upgrade" with network unplugged and I login with persistence enabled 2:10.968
Then all tps features from the old Tails version are active 1.666
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.029
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.295
After features/support/hooks.rb:330 0.809
After features/support/hooks.rb:100 0.007
6:59.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.529
And no SquashFS delta is installed 0.208
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.506
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.064
And Tor is ready 21.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.694
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.531
Given I shutdown Tails and wait for the computer to power off 13.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.562
Then Tails is running version 6.2~testoverlayfs 0.050
And all tps features are active 2.464
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.340
When the network is plugged 0.065
And Tor is ready 18.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.537
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.462
Given I shutdown Tails and wait for the computer to power off 4.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.467
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.268
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.068
And Tor is ready 48.557
Then the Upgrader considers the system as up-to-date 0.301
# 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.314
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.403
After features/support/hooks.rb:330 0.769
After features/support/hooks.rb:100 0.014
38.204
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.251
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.155
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.334
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.843
After features/support/hooks.rb:330 1.281
After features/support/hooks.rb:100 0.000