Project Number Date
test_Tails_ISO_stable 5145 05 Oct 2024, 12:20

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 18:48.843 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.074
Before features/support/hooks.rb:269 0.010
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.166
When I start Tails from USB drive "old" with network unplugged 1:38.639
Then the boot device has safe access rights 2.968
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 7.195
After features/support/hooks.rb:100 0.009
Tags: @product
1:59.464
Before features/support/hooks.rb:269 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:18.743
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 29.883
And I take note of which tps features are available 1.338
Then a Tails persistence partition exists on USB drive "old" 0.725
And I shutdown Tails and wait for the computer to power off 8.252
After features/support/hooks.rb:326 0.133
After features/support/hooks.rb:100 0.010
Tags: @product
2:45.445
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.724
Then Tails is running from USB drive "old" 0.759
And all tps features are active 1.982
When I write some files expected to persist 1.819
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.728
And all persistent directories from the old Tails version have safe access rights 2.210
And I take note of which tps features are available 0.368
And I shutdown Tails and wait for the computer to power off 4.366
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.042
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.699
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.262
And I log in to a new session 17.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.692
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.056
Then the running Tails is installed on USB drive "to_upgrade" 17.153
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 2.403
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.238
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.288
Then all tps features from the old Tails version are active 1.516
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.287
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.242
After features/support/hooks.rb:326 0.989
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:35.944
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 13.786
And no SquashFS delta is installed 0.952
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
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.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.072
And Tor is ready 21.917
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.485
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.787
Given I shutdown Tails and wait for the computer to power off 10.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.098
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.266
# 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.279
When the network is plugged 0.068
And Tor is ready 19.851
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.952
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.865
Given I shutdown Tails and wait for the computer to power off 4.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.094
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.034
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.068
And Tor is ready 17.117
Then the Upgrader considers the system as up-to-date 10.812
# 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 13.898
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.915
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.977
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 11.909
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
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.762
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.381
After features/support/hooks.rb:326 1.669
After features/support/hooks.rb:100 0.000