Project Number Date
test_Tails_ISO_stable 4591 25 Dec 2023, 17:27

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 17:10.799 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:31.512
Before features/support/hooks.rb:245 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 18.659
When I start Tails from USB drive "old" with network unplugged 1:7.385
Then the boot device has safe access rights 3.219
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:291 3.656
After features/support/hooks.rb:75 0.010
Tags: @product
1:53.565
Before features/support/hooks.rb:245 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:1.950
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 42.441
And I take note of which tps features are available 1.641
Then a Tails persistence partition exists on USB drive "old" 0.892
And I shutdown Tails and wait for the computer to power off 6.126
After features/support/hooks.rb:291 0.113
After features/support/hooks.rb:75 0.010
Tags: @product
2:16.193
Before features/support/hooks.rb:245 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.249
Then Tails is running from USB drive "old" 0.394
And all tps features are active 2.440
When I write some files expected to persist 1.982
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.666
And all persistent directories from the old Tails version have safe access rights 2.827
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 3.071
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.671
After features/support/hooks.rb:291 0.145
After features/support/hooks.rb:75 0.010
Tags: @product
2:37.690
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.490
And I log in to a new session 16.456
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.152
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.209
Then the running Tails is installed on USB drive "to_upgrade" 13.498
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:291 6.887
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.340
Before features/support/hooks.rb:245 0.007
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.226
Then all tps features from the old Tails version are active 1.581
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.639
And the expected persistent files created with the old Tails version are present in the filesystem 1.598
And all persistent directories from the old Tails version have safe access rights 2.717
After features/support/hooks.rb:291 0.671
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:26.559
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 11.259
And no SquashFS delta is installed 0.185
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.295
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.072
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.386
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.632
When the network is plugged 0.035
And Tor is ready 20.760
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.601
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.308
Given I shutdown Tails and wait for the computer to power off 7.137
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.413
Then Tails is running version 2.2~testoverlayfsng 0.117
And all tps features are active 2.697
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.421
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.263
# 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.484
When the network is plugged 0.050
And Tor is ready 43.658
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.588
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.616
Given I shutdown Tails and wait for the computer to power off 4.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.422
Then Tails is running version 2.3~testoverlayfsng 0.134
And all tps features are active 2.509
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.578
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.293
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.277
When the network is plugged 0.064
And Tor is ready 15.202
Then the Upgrader considers the system as up-to-date 11.024
# 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.207
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.389
After features/support/hooks.rb:291 0.803
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
29.938
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.854
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.441
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the signing key used by the Upgrader is outdated 0.645
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 16.107
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.777
After features/support/hooks.rb:291 0.851
After features/support/hooks.rb:75 0.000