Project Number Date
test_Tails_ISO_devel 3743 18 Mar 2025, 13:24

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:36.150 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:18.319
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.307
When I start Tails from USB drive "old" with network unplugged 1:41.412
Then the boot device has safe access rights 3.192
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 8.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login 1:29.345
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 31.092
And I take note of which tps features are available 1.451
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.313
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.072
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.763
Then Tails is running from USB drive "old" 0.420
And all tps features are active 1.933
When I write some files expected to persist 1.944
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.490
And I take note of which tps features are available 0.449
And I shutdown Tails and wait for the computer to power off 4.349
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.817
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.567
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.115
And I log in to a new session 18.591
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.508
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.828
Then the running Tails is installed on USB drive "to_upgrade" 26.659
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:330 3.573
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.609
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:21.621
Then all tps features from the old Tails version are active 1.898
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.517
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.521
After features/support/hooks.rb:330 1.655
After features/support/hooks.rb:100 0.010
6:30.107
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 with a persistent partition enabled and logged in 11.332
And no SquashFS delta is installed 0.237
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.068
And Tor is ready 18.291
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.722
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.130
Given I shutdown Tails and wait for the computer to power off 8.930
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.041
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.446
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.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.260
When the network is plugged 0.078
And Tor is ready 19.913
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.510
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.245
Given I shutdown Tails and wait for the computer to power off 4.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.149
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.278
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.282
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.062
And Tor is ready 15.765
Then the Upgrader considers the system as up-to-date 0.400
# 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.721
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.895
After features/support/hooks.rb:330 0.984
After features/support/hooks.rb:100 0.032
36.833
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 with a persistent partition enabled and logged in 11.328
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.140
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 17.958
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.800
After features/support/hooks.rb:330 0.689
After features/support/hooks.rb:100 0.000