Project Number Date
test_Tails_ISO_stable 4522 23 Nov 2023, 12:28

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 18:15.466 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
1:41.209
Before features/support/hooks.rb:245 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 20.579
When I start Tails from USB drive "old" with network unplugged 1:14.991
Then the boot device has safe access rights 3.255
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.244
After features/support/hooks.rb:290 3.727
After features/support/hooks.rb:75 0.010
Tags: @product
2:0.494
Before features/support/hooks.rb:245 0.012
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:5.100
Then Tails is running from USB drive "old" 0.527
And I create a persistent partition 45.076
And I take note of which tps features are available 1.615
Then a Tails persistence partition exists on USB drive "old" 0.913
And I shutdown Tails and wait for the computer to power off 7.069
After features/support/hooks.rb:290 0.179
After features/support/hooks.rb:75 0.010
Tags: @product
2:32.821
Before features/support/hooks.rb:245 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:56.486
Then Tails is running from USB drive "old" 0.372
And all tps features are active 8.542
When I write some files expected to persist 2.099
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.755
And all persistent directories from the old Tails version have safe access rights 3.118
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.154
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.331
After features/support/hooks.rb:290 0.109
After features/support/hooks.rb:75 0.012
Tags: @product
2:40.613
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.446
And I log in to a new session 14.456
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.444
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.776
Then the running Tails is installed on USB drive "to_upgrade" 17.691
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:290 1.912
After features/support/hooks.rb:75 0.000
Tags: @product
2:10.119
Before features/support/hooks.rb:245 0.008
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.104
Then all tps features from the old Tails version are active 8.291
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 4.134
And the expected persistent files created with the old Tails version are present in the filesystem 1.637
And all persistent directories from the old Tails version have safe access rights 3.345
After features/support/hooks.rb:290 0.770
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
6:36.166
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.296
And no SquashFS delta is installed 0.205
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.433
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.403
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.555
When the network is plugged 0.038
And Tor is ready 17.505
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.842
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.010
Given I shutdown Tails and wait for the computer to power off 8.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.843
Then Tails is running version 2.2~testoverlayfsng 0.121
And all tps features are active 10.367
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.466
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.107
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.311
When the network is plugged 0.041
And Tor is ready 17.008
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.722
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.639
Given I shutdown Tails and wait for the computer to power off 4.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.647
Then Tails is running version 2.3~testoverlayfsng 0.141
And all tps features are active 19.539
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.572
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.083
# 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.542
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.300
When the network is plugged 0.062
And Tor is ready 16.463
Then the Upgrader considers the system as up-to-date 0.271
# 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 29.030
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.449
After features/support/hooks.rb:290 1.057
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
34.041
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.420
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.635
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.131
And the signing key used by the Upgrader is outdated 0.634
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 17.513
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.641
After features/support/hooks.rb:290 0.787
After features/support/hooks.rb:75 0.000