Project Number Date
test_Tails_ISO_stable 4998 05 Aug 2024, 14:46

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:3.080 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:31.332
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.393
When I start Tails from USB drive "old" with network unplugged 1:54.320
Then the boot device has safe access rights 3.200
And Tails is running from USB drive "old" 0.360
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.295
After features/support/hooks.rb:326 3.536
After features/support/hooks.rb:100 0.034
Tags: @product
2:8.174
Before features/support/hooks.rb:269 0.006
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:22.891
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 33.122
And I take note of which tps features are available 1.473
Then a Tails persistence partition exists on USB drive "old" 0.937
And I shutdown Tails and wait for the computer to power off 9.201
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.993
Before features/support/hooks.rb:269 0.007
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.403
Then Tails is running from USB drive "old" 0.406
And all tps features are active 1.987
When I write some files expected to persist 2.006
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 2.540
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.486
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.775
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.692
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 12.331
And I log in to a new session 21.415
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.664
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.197
Then the running Tails is installed on USB drive "to_upgrade" 22.237
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 2.288
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.860
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.303
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.437
And the boot device has safe access rights 3.319
And the expected persistent files created with the old Tails version are present in the filesystem 1.396
And all persistent directories from the old Tails version have safe access rights 2.485
After features/support/hooks.rb:326 1.042
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:48.372
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.892
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.029
And Tor is ready 18.391
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.706
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.898
Given I shutdown Tails and wait for the computer to power off 8.767
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.858
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.448
And the file system changes introduced in version 6.2~testoverlayfs are present 0.366
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.037
And Tor is ready 17.770
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.016
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.584
Given I shutdown Tails and wait for the computer to power off 4.368
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.655
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.540
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.397
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.041
And Tor is ready 45.084
Then the Upgrader considers the system as up-to-date 0.333
# 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.856
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.074
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.655
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 10.340
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 1.072
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 19.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.610
After features/support/hooks.rb:326 0.702
After features/support/hooks.rb:100 0.000