Project Number Date
test_Tails_ISO_stable 5011 08 Aug 2024, 14:32

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:4.268 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:54.199
Before features/support/hooks.rb:269 0.007
Given a computer 0.261
And I create a 7200 MiB disk named "old" 0.080
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 46.093
When I start Tails from USB drive "old" with network unplugged 2:2.005
Then the boot device has safe access rights 3.486
And Tails is running from USB drive "old" 0.408
And there is no persistence partition on USB drive "old" 0.093
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.254
After features/support/hooks.rb:326 3.874
After features/support/hooks.rb:100 0.011
Tags: @product
2:18.148
Before features/support/hooks.rb:269 0.008
Given a computer 0.265
And I start Tails from USB drive "old" with network unplugged and I login 1:29.430
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 35.869
And I take note of which tps features are available 2.371
Then a Tails persistence partition exists on USB drive "old" 0.913
And I shutdown Tails and wait for the computer to power off 8.959
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.668
Before features/support/hooks.rb:269 0.007
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.302
Then Tails is running from USB drive "old" 0.321
And all tps features are active 4.767
When I write some files expected to persist 1.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.287
And all persistence configuration files have safe access rights 0.610
And all persistent directories from the old Tails version have safe access rights 2.677
And I take note of which tps features are available 0.655
And I shutdown Tails and wait for the computer to power off 6.998
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.959
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.173
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.093
And I log in to a new session 19.647
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.697
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.233
Then the running Tails is installed on USB drive "to_upgrade" 20.558
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 3.562
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.055
Before features/support/hooks.rb:269 0.006
Given a computer 0.333
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.888
Then all tps features from the old Tails version are active 1.835
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.301
And the expected persistent files created with the old Tails version are present in the filesystem 1.560
And all persistent directories from the old Tails version have safe access rights 2.744
After features/support/hooks.rb:326 0.894
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:55.512
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 36.491
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.587
When the network is plugged 0.088
And Tor is ready 24.715
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.514
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.006
Given I shutdown Tails and wait for the computer to power off 11.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.400
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 2.593
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.368
# 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.300
When the network is plugged 0.068
And Tor is ready 19.586
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.863
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.334
Given I shutdown Tails and wait for the computer to power off 4.493
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.256
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.416
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.071
And Tor is ready 16.890
Then the Upgrader considers the system as up-to-date 0.346
# 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.060
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.999
After features/support/hooks.rb:326 0.744
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.511
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.988
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 20.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.902
After features/support/hooks.rb:326 0.760
After features/support/hooks.rb:100 0.000