Project Number Date
test_Tails_ISO_20872-more-gtk-launch 10 05 Apr 2025, 07:55

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:56.750 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:12.652
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 34.861
When I start Tails from USB drive "old" with network unplugged 1:31.834
Then the boot device has safe access rights 3.514
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:330 3.924
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.186
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:29.274
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 32.083
And I take note of which tps features are available 1.849
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.581
After features/support/hooks.rb:330 0.229
After features/support/hooks.rb:100 0.012
Tags: @product
2:57.766
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.216
Then Tails is running from USB drive "old" 0.432
And all tps features are active 2.222
When I write some files expected to persist 2.022
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
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.553
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.363
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.575
After features/support/hooks.rb:330 0.120
After features/support/hooks.rb:100 0.012
Tags: @product
2:53.607
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 25.071
And I log in to a new session 21.436
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.399
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.967
Then the running Tails is installed on USB drive "to_upgrade" 26.715
And I unplug USB drive "to_upgrade" 0.254
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:330 0.886
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.729
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.326
Then all tps features from the old Tails version are active 1.847
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 3.802
And the expected persistent files created with the old Tails version are present in the filesystem 1.575
And all persistent directories from the old Tails version have safe access rights 2.549
After features/support/hooks.rb:330 1.186
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:45.489
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.507
And no SquashFS delta is installed 0.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.072
And Tor is ready 22.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.347
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.167
Given I shutdown Tails and wait for the computer to power off 8.995
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.292
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 5.176
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.105
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.440
# 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.326
When the network is plugged 0.106
And Tor is ready 19.326
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.070
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.843
Given I shutdown Tails and wait for the computer to power off 4.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.222
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.330
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.068
And Tor is ready 16.393
Then the Upgrader considers the system as up-to-date 10.953
# 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 16.463
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.856
After features/support/hooks.rb:330 0.689
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.318
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 9.917
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.451
After features/support/hooks.rb:330 1.399
After features/support/hooks.rb:100 0.000