Project Number Date
test_Tails_ISO_devel 3647 14 Jan 2025, 17:35

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:13.127 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
1:56.119
Before features/support/hooks.rb:269 0.003
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 29.147
When I start Tails from USB drive "old" with network unplugged 1:21.804
Then the boot device has safe access rights 2.852
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 6.823
After features/support/hooks.rb:100 0.006
Tags: @product
2:2.437
Before features/support/hooks.rb:269 0.002
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:20.448
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 30.994
And I take note of which tps features are available 1.390
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.296
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.006
Tags: @product
2:48.079
Before features/support/hooks.rb:269 0.003
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.660
Then Tails is running from USB drive "old" 0.333
And all tps features are active 1.987
When I write some files expected to persist 1.862
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.335
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.292
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.545
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.020
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.006
Tags: @product
2:35.322
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.338
And I log in to a new session 17.351
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.672
And I plug USB drive "to_upgrade" 2.372
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.320
Then the running Tails is installed on USB drive "to_upgrade" 25.827
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 6.741
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.938
Before features/support/hooks.rb:269 0.003
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.327
Then all tps features from the old Tails version are active 1.804
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.398
And the expected persistent files created with the old Tails version are present in the filesystem 1.424
And all persistent directories from the old Tails version have safe access rights 2.404
After features/support/hooks.rb:326 0.903
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
7:3.670
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 57.886
And no SquashFS delta is installed 0.398
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.081
And Tor is ready 19.525
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.578
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.669
Given I shutdown Tails and wait for the computer to power off 8.569
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.731
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.547
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.382
When the network is plugged 0.085
And Tor is ready 18.412
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.420
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.849
Given I shutdown Tails and wait for the computer to power off 4.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.881
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.071
And Tor is ready 17.675
Then the Upgrader considers the system as up-to-date 0.312
# 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 14.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.892
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
34.560
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.729
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.609
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
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.074
And Tor is ready 18.912
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.064
After features/support/hooks.rb:326 1.241
After features/support/hooks.rb:100 0.000