Project Number Date
test_Tails_ISO_stable 5294 26 Nov 2024, 21:21

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:39.489 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:35.277
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 41.029
When I start Tails from USB drive "old" with network unplugged 1:48.470
Then the boot device has safe access rights 3.324
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.385
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 7.536
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.778
Before features/support/hooks.rb:269 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:36.936
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 35.751
And I take note of which tps features are available 1.828
Then a Tails persistence partition exists on USB drive "old" 0.996
And I shutdown Tails and wait for the computer to power off 8.698
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.659
Before features/support/hooks.rb:269 0.008
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.207
Then Tails is running from USB drive "old" 0.511
And all tps features are active 2.258
When I write some files expected to persist 2.418
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 2.726
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 4.239
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.942
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.639
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 12.709
And I log in to a new session 20.681
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.799
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.420
Then the running Tails is installed on USB drive "to_upgrade" 23.066
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.288
After features/support/hooks.rb:326 2.930
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.983
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.710
Then all tps features from the old Tails version are active 1.911
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.588
And the expected persistent files created with the old Tails version are present in the filesystem 1.724
And all persistent directories from the old Tails version have safe access rights 2.481
After features/support/hooks.rb:326 0.632
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:39.990
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 12.422
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.243
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.082
And Tor is ready 22.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.860
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.968
Given I shutdown Tails and wait for the computer to power off 11.545
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.016
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.404
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.307
When the network is plugged 0.094
And Tor is ready 19.298
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.187
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.290
Given I shutdown Tails and wait for the computer to power off 4.910
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.765
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.269
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.384
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.132
And Tor is ready 20.115
Then the Upgrader considers the system as up-to-date 0.364
# 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.434
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.141
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
46.160
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 12.221
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 1.189
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 24.503
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.692
After features/support/hooks.rb:326 0.965
After features/support/hooks.rb:100 0.000