Project Number Date
test_Tails_ISO_stable 4615 11 Jan 2024, 15:42

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:41.657 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.527
Before features/support/hooks.rb:245 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 21.931
When I start Tails from USB drive "old" with network unplugged 56.368
Then the boot device has safe access rights 3.027
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:291 3.514
After features/support/hooks.rb:75 0.042
Tags: @product
1:54.787
Before features/support/hooks.rb:245 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:0.467
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 44.424
And I take note of which tps features are available 1.471
Then a Tails persistence partition exists on USB drive "old" 0.829
And I shutdown Tails and wait for the computer to power off 7.081
After features/support/hooks.rb:291 0.179
After features/support/hooks.rb:75 0.009
Tags: @product
2:13.581
Before features/support/hooks.rb:245 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:47.685
Then Tails is running from USB drive "old" 0.351
And all tps features are active 2.066
When I write some files expected to persist 1.806
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.566
And all persistent directories from the old Tails version have safe access rights 2.646
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 3.057
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.498
After features/support/hooks.rb:291 0.146
After features/support/hooks.rb:75 0.009
Tags: @product
2:28.079
Before features/support/hooks.rb:245 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 9.209
And I log in to a new session 16.036
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.034
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.719
Then the running Tails is installed on USB drive "to_upgrade" 12.282
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:291 6.761
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.418
Before features/support/hooks.rb:245 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.351
Then all tps features from the old Tails version are active 1.722
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.416
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 2.847
After features/support/hooks.rb:291 0.644
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:12.941
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.553
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.348
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.134
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.320
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.592
When the network is plugged 0.032
And Tor is ready 16.543
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.630
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.291
Given I shutdown Tails and wait for the computer to power off 5.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.280
Then Tails is running version 2.2~testoverlayfsng 0.094
And all tps features are active 2.130
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.395
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.250
# 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.264
When the network is plugged 0.055
And Tor is ready 44.881
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.550
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.874
Given I shutdown Tails and wait for the computer to power off 3.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.835
Then Tails is running version 2.3~testoverlayfsng 0.099
And all tps features are active 2.135
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.506
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.062
# 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.288
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.272
When the network is plugged 0.049
And Tor is ready 16.746
Then the Upgrader considers the system as up-to-date 0.244
# 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 26.844
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.012
After features/support/hooks.rb:291 0.811
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
29.321
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 9.576
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.425
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.064
And the signing key used by the Upgrader is outdated 1.031
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 16.587
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.596
After features/support/hooks.rb:291 0.738
After features/support/hooks.rb:75 0.000