Project Number Date
test_Tails_ISO_tca-misc-improvements 10 17 Apr 2025, 18:40

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:21.818 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:15.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.352
When I start Tails from USB drive "old" with network unplugged 1:37.081
Then the boot device has safe access rights 3.327
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.389
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 3.780
After features/support/hooks.rb:100 0.006
Tags: @product
2:22.819
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:39.252
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 31.724
And I take note of which tps features are available 2.233
Then a Tails persistence partition exists on USB drive "old" 0.836
And I shutdown Tails and wait for the computer to power off 8.253
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.031
Then Tails is running from USB drive "old" 0.361
And all tps features are active 2.054
When I write some files expected to persist 1.878
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.740
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 4.372
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.559
After features/support/hooks.rb:330 0.103
After features/support/hooks.rb:100 0.007
Tags: @product
2:44.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.018
And I log in to a new session 22.264
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.834
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.536
Then the running Tails is installed on USB drive "to_upgrade" 28.918
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 1.001
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.061
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.240
Then all tps features from the old Tails version are active 1.596
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.582
And the expected persistent files created with the old Tails version are present in the filesystem 1.427
And all persistent directories from the old Tails version have safe access rights 2.723
After features/support/hooks.rb:330 1.357
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:1.759
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.093
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.530
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.549
When the network is plugged 0.086
And Tor is ready 52.046
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.722
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.124
Given I shutdown Tails and wait for the computer to power off 8.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.487
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.411
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.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.290
When the network is plugged 0.074
And Tor is ready 18.094
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.566
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.561
Given I shutdown Tails and wait for the computer to power off 4.396
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.364
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.192
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.062
And Tor is ready 17.283
Then the Upgrader considers the system as up-to-date 0.327
# 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.812
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.636
After features/support/hooks.rb:330 0.819
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
41.186
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.342
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.766
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.109
But a current signing key is available on our website 0.000
When the network is plugged 0.112
And Tor is ready 22.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.582
After features/support/hooks.rb:330 0.654
After features/support/hooks.rb:100 0.000