Project Number Date
test_Tails_ISO_stable 4600 03 Jan 2024, 12:18

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:48.777 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:24.810
Before features/support/hooks.rb:245 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 17.822
When I start Tails from USB drive "old" with network unplugged 1:1.669
Then the boot device has safe access rights 3.121
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:291 3.480
After features/support/hooks.rb:75 0.008
Tags: @product
1:56.250
Before features/support/hooks.rb:245 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:5.401
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 41.885
And I take note of which tps features are available 1.611
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 6.060
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.009
Tags: @product
2:18.832
Before features/support/hooks.rb:245 0.004
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.226
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.068
When I write some files expected to persist 1.809
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.619
And all persistent directories from the old Tails version have safe access rights 2.436
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.131
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.244
After features/support/hooks.rb:291 0.113
After features/support/hooks.rb:75 0.009
Tags: @product
2:31.211
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 11.007
And I log in to a new session 16.217
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.289
And I plug USB drive "to_upgrade" 2.536
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.184
Then the running Tails is installed on USB drive "to_upgrade" 12.612
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 0.871
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.677
Before features/support/hooks.rb:245 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.194
Then all tps features from the old Tails version are active 1.591
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.529
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 3.198
After features/support/hooks.rb:291 0.742
After features/support/hooks.rb:75 0.009
6:15.236
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 12.171
And no SquashFS delta is installed 0.214
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.461
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.086
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.407
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.530
When the network is plugged 0.032
And Tor is ready 15.473
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.795
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.263
Given I shutdown Tails and wait for the computer to power off 6.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.440
Then Tails is running version 2.2~testoverlayfsng 0.099
And all tps features are active 2.379
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.439
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.307
When the network is plugged 0.055
And Tor is ready 43.851
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.589
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.646
Given I shutdown Tails and wait for the computer to power off 4.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.184
Then Tails is running version 2.3~testoverlayfsng 0.104
And all tps features are active 2.173
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.677
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.082
# 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.285
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.310
When the network is plugged 0.063
And Tor is ready 17.068
Then the Upgrader considers the system as up-to-date 0.264
# 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 27.541
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.211
After features/support/hooks.rb:291 0.836
After features/support/hooks.rb:75 0.018
26.758
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.298
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.362
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.089
And the signing key used by the Upgrader is outdated 0.594
But a current signing key is available on our website 0.000
When the network is plugged 0.169
And Tor is ready 14.581
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.661
After features/support/hooks.rb:291 1.353
After features/support/hooks.rb:75 0.000