Project Number Date
test_Tails_ISO_stable 5029 14 Aug 2024, 12:28

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:55.263 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:9.062
Before features/support/hooks.rb:269 0.006
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.018
When I start Tails from USB drive "old" with network unplugged 1:31.751
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.775
After features/support/hooks.rb:100 0.012
Tags: @product
2:6.256
Before features/support/hooks.rb:269 0.007
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login 1:23.860
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 31.101
And I take note of which tps features are available 1.346
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 8.564
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.012
Tags: @product
2:54.592
Before features/support/hooks.rb:269 0.007
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.441
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.032
When I write some files expected to persist 1.834
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.329
And I take note of which tps features are available 0.388
And I shutdown Tails and wait for the computer to power off 4.263
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.205
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.771
Before features/support/hooks.rb:269 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 11.118
And I log in to a new session 18.124
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.759
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.392
Then the running Tails is installed on USB drive "to_upgrade" 22.560
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.454
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.925
Before features/support/hooks.rb:269 0.007
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.521
Then all tps features from the old Tails version are active 1.573
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.412
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.418
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:23.615
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.205
And no SquashFS delta is installed 0.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.063
And Tor is ready 20.794
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.093
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.109
Given I shutdown Tails and wait for the computer to power off 1:18.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.115
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.065
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.280
When the network is plugged 0.076
And Tor is ready 17.071
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 8.217
Given I shutdown Tails and wait for the computer to power off 4.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.122
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.995
And the file system changes introduced in version 6.3~testoverlayfs are present 0.508
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.491
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.359
When the network is plugged 0.075
And Tor is ready 19.055
Then the Upgrader considers the system as up-to-date 0.321
# 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.026
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.017
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.039
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.809
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.782
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 20.885
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.033
After features/support/hooks.rb:326 0.686
After features/support/hooks.rb:100 0.000