Project Number Date
test_Tails_ISO_devel 3564 28 Oct 2024, 12:55

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 21:17.919 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:22.621
Before features/support/hooks.rb:269 0.006
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.071
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 32.573
When I start Tails from USB drive "old" with network unplugged 1:42.843
Then the boot device has safe access rights 4.348
And Tails is running from USB drive "old" 0.491
And there is no persistence partition on USB drive "old" 0.103
And process "udev-watchdog" is running 0.138
And udev-watchdog is monitoring the correct device 0.474
And I unplug USB drive "old" 0.267
After features/support/hooks.rb:326 7.512
After features/support/hooks.rb:100 0.023
Tags: @product
2:24.649
Before features/support/hooks.rb:269 0.011
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login 1:36.505
Then Tails is running from USB drive "old" 0.471
And I create a persistent partition 34.931
And I take note of which tps features are available 2.241
Then a Tails persistence partition exists on USB drive "old" 0.966
And I shutdown Tails and wait for the computer to power off 9.248
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.013
Tags: @product
3:21.631
Before features/support/hooks.rb:269 0.008
Given a computer 0.297
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.076
Then Tails is running from USB drive "old" 0.801
And all tps features are active 9.853
When I write some files expected to persist 2.087
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 3.082
And I take note of which tps features are available 3.232
And I shutdown Tails and wait for the computer to power off 6.519
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.005
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.011
Tags: @product
3:3.391
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 30.037
And I log in to a new session 21.915
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.730
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.941
Then the running Tails is installed on USB drive "to_upgrade" 22.943
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 2.440
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.384
Before features/support/hooks.rb:269 0.008
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.075
Then all tps features from the old Tails version are active 1.831
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.797
And the expected persistent files created with the old Tails version are present in the filesystem 1.683
And all persistent directories from the old Tails version have safe access rights 2.436
After features/support/hooks.rb:326 0.621
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
7:1.500
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 17.178
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.120
And Tor is ready 25.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.823
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.155
Given I shutdown Tails and wait for the computer to power off 11.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.943
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.685
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.320
When the network is plugged 0.090
And Tor is ready 20.917
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.293
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.128
Given I shutdown Tails and wait for the computer to power off 4.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.712
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.313
And the file system changes introduced in version 6.3~testoverlayfs are present 0.602
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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.096
And Tor is ready 20.802
Then the Upgrader considers the system as up-to-date 0.339
# 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.292
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.998
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.074
Tags: @product @automatic_upgrade
42.739
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 11.519
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.829
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 21.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.368
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.000