Project Number Date
test_Tails_ISO_stable 4546 02 Dec 2023, 12:06

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 16:34.370 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:23.162
Before features/support/hooks.rb:245 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 20.126
When I start Tails from USB drive "old" with network unplugged 57.963
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:291 3.450
After features/support/hooks.rb:75 0.093
Tags: @product
1:58.087
Before features/support/hooks.rb:245 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:3.538
Then Tails is running from USB drive "old" 0.499
And I create a persistent partition 45.298
And I take note of which tps features are available 1.517
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 6.159
After features/support/hooks.rb:291 0.123
After features/support/hooks.rb:75 0.010
Tags: @product
2:15.870
Before features/support/hooks.rb:245 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:48.151
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.025
When I write some files expected to persist 1.617
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 1.087
And all persistent directories from the old Tails version have safe access rights 2.607
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 3.069
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.017
After features/support/hooks.rb:291 0.122
After features/support/hooks.rb:75 0.009
Tags: @product
2:32.367
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 10.264
And I log in to a new session 16.328
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.302
And I plug USB drive "to_upgrade" 2.553
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.078
Then the running Tails is installed on USB drive "to_upgrade" 12.446
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:291 7.244
After features/support/hooks.rb:75 0.000
Tags: @product
2:3.556
Before features/support/hooks.rb:245 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.577
Then all tps features from the old Tails version are active 1.641
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.637
And the expected persistent files created with the old Tails version are present in the filesystem 1.522
And all persistent directories from the old Tails version have safe access rights 2.644
After features/support/hooks.rb:291 0.724
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:50.825
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 10.774
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.426
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.099
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.446
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.627
When the network is plugged 0.047
And Tor is ready 17.535
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.783
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.639
Given I shutdown Tails and wait for the computer to power off 6.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.332
Then Tails is running version 2.2~testoverlayfsng 0.105
And all tps features are active 2.266
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.374
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.285
When the network is plugged 0.039
And Tor is ready 15.582
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.623
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.976
Given I shutdown Tails and wait for the computer to power off 3.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.780
Then Tails is running version 2.3~testoverlayfsng 0.119
And all tps features are active 2.039
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.675
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.106
# 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.291
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.294
When the network is plugged 0.051
And Tor is ready 16.298
Then the Upgrader considers the system as up-to-date 0.302
# 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 25.460
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.158
After features/support/hooks.rb:291 0.804
After features/support/hooks.rb:75 0.030
Tags: @product @automatic_upgrade
30.499
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.790
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.201
And the signing key used by the Upgrader is outdated 1.587
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 15.753
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.773
After features/support/hooks.rb:291 0.696
After features/support/hooks.rb:75 0.000