Project Number Date
test_Tails_ISO_stable 5369 07 Jan 2025, 03:37

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:51.433 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:37.497
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 34.097
When I start Tails from USB drive "old" with network unplugged 1:57.157
Then the boot device has safe access rights 3.632
And Tails is running from USB drive "old" 0.391
And there is no persistence partition on USB drive "old" 0.108
And process "udev-watchdog" is running 0.133
And udev-watchdog is monitoring the correct device 0.367
And I unplug USB drive "old" 0.254
After features/support/hooks.rb:326 3.644
After features/support/hooks.rb:100 0.012
Tags: @product
2:19.734
Before features/support/hooks.rb:269 0.006
Given a computer 0.260
And I start Tails from USB drive "old" with network unplugged and I login 1:27.179
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 40.730
And I take note of which tps features are available 1.633
Then a Tails persistence partition exists on USB drive "old" 0.882
And I shutdown Tails and wait for the computer to power off 8.707
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
3:20.054
Before features/support/hooks.rb:269 0.004
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:39.007
Then Tails is running from USB drive "old" 1.925
And all tps features are active 2.325
When I write some files expected to persist 3.224
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.490
And all persistent directories from the old Tails version have safe access rights 2.634
And I take note of which tps features are available 0.549
And I shutdown Tails and wait for the computer to power off 4.389
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.032
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.550
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.778
And I log in to a new session 22.424
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.838
And I plug USB drive "to_upgrade" 2.565
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.219
Then the running Tails is installed on USB drive "to_upgrade" 25.242
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 2.226
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.573
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.348
Then all tps features from the old Tails version are active 1.849
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.387
And the expected persistent files created with the old Tails version are present in the filesystem 1.626
And all persistent directories from the old Tails version have safe access rights 2.777
After features/support/hooks.rb:326 0.908
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
6:50.200
Before features/support/hooks.rb:269 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.640
And no SquashFS delta is installed 0.448
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.236
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.596
When the network is plugged 0.194
And Tor is ready 23.772
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.112
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.802
Given I shutdown Tails and wait for the computer to power off 11.915
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.750
Then Tails is running version 6.2~testoverlayfs 0.059
And all tps features are active 2.512
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.491
# 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.868
When the network is plugged 0.080
And Tor is ready 19.717
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.498
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.671
Given I shutdown Tails and wait for the computer to power off 4.601
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.701
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.161
And the file system changes introduced in version 6.3~testoverlayfs are present 0.614
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.388
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.075
And Tor is ready 19.612
Then the Upgrader considers the system as up-to-date 0.307
# 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.810
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.020
After features/support/hooks.rb:326 0.803
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.820
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.895
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.745
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 19.743
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.207
After features/support/hooks.rb:326 1.006
After features/support/hooks.rb:100 0.000