Project Number Date
test_Tails_ISO_stable 4911 24 Jun 2024, 12:39

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:26.174 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:42.166
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.612
When I start Tails from USB drive "old" with network unplugged 2:4.630
Then the boot device has safe access rights 3.388
And Tails is running from USB drive "old" 0.520
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.772
After features/support/hooks.rb:100 0.013
Tags: @product
2:13.981
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:30.073
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 32.271
And I take note of which tps features are available 1.527
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 8.780
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.821
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.102
Then Tails is running from USB drive "old" 0.328
And all tps features are active 1.997
When I write some files expected to persist 1.692
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.325
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.563
And I take note of which tps features are available 0.407
And I shutdown Tails and wait for the computer to power off 4.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.408
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.180
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.284
And I log in to a new session 18.626
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.662
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.520
Then the running Tails is installed on USB drive "to_upgrade" 17.246
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:326 2.735
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.364
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.952
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.417
And the boot device has safe access rights 3.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.332
After features/support/hooks.rb:326 1.037
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:25.619
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 25.481
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.085
And Tor is ready 17.395
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.774
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.136
Given I shutdown Tails and wait for the computer to power off 8.641
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.524
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
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.338
# 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.331
When the network is plugged 0.042
And Tor is ready 19.862
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.163
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.911
Given I shutdown Tails and wait for the computer to power off 4.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.302
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.083
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.066
And Tor is ready 20.784
Then the Upgrader considers the system as up-to-date 0.332
# 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 15.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.828
After features/support/hooks.rb:326 0.790
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.040
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.466
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.814
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 18.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.924
After features/support/hooks.rb:326 1.337
After features/support/hooks.rb:100 0.000