Project Number Date
test_Tails_ISO_stable 4611 10 Jan 2024, 17:11

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:21.160 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:32.175
Before features/support/hooks.rb:245 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 20.413
When I start Tails from USB drive "old" with network unplugged 1:6.311
Then the boot device has safe access rights 3.168
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:291 3.578
After features/support/hooks.rb:75 0.018
Tags: @product
2:1.716
Before features/support/hooks.rb:245 0.005
Given a computer 0.540
And I start Tails from USB drive "old" with network unplugged and I login 1:7.829
Then Tails is running from USB drive "old" 0.423
And I create a persistent partition 43.617
And I take note of which tps features are available 1.423
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 7.069
After features/support/hooks.rb:291 0.112
After features/support/hooks.rb:75 0.010
Tags: @product
2:20.920
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 with persistence enabled 1:52.124
Then Tails is running from USB drive "old" 0.423
And all tps features are active 2.211
When I write some files expected to persist 2.179
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.328
And all persistence configuration files have safe access rights 0.768
And all persistent directories from the old Tails version have safe access rights 3.147
And I take note of which tps features are available 0.533
And I shutdown Tails and wait for the computer to power off 3.068
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.941
After features/support/hooks.rb:291 0.171
After features/support/hooks.rb:75 0.012
Tags: @product
2:41.009
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.295
And I log in to a new session 21.506
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.120
And I plug USB drive "to_upgrade" 2.508
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.878
Then the running Tails is installed on USB drive "to_upgrade" 14.316
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:291 0.724
After features/support/hooks.rb:75 0.000
Tags: @product
2:7.457
Before features/support/hooks.rb:245 0.009
Given a computer 0.695
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.133
Then all tps features from the old Tails version are active 2.879
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.747
And the expected persistent files created with the old Tails version are present in the filesystem 1.863
And all persistent directories from the old Tails version have safe access rights 2.774
After features/support/hooks.rb:291 0.615
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
6:6.976
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.768
And no SquashFS delta is installed 0.150
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.439
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.053
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.415
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.599
When the network is plugged 0.047
And Tor is ready 16.360
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.858
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.218
Given I shutdown Tails and wait for the computer to power off 6.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.496
Then Tails is running version 2.2~testoverlayfsng 0.174
And all tps features are active 5.488
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.402
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.348
When the network is plugged 0.043
And Tor is ready 18.212
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.103
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.355
Given I shutdown Tails and wait for the computer to power off 4.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.496
Then Tails is running version 2.3~testoverlayfsng 0.102
And all tps features are active 3.093
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.605
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.284
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.306
When the network is plugged 0.038
And Tor is ready 16.722
Then the Upgrader considers the system as up-to-date 0.285
# 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.377
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.878
After features/support/hooks.rb:291 0.883
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
30.904
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.351
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.077
And the signing key used by the Upgrader is outdated 1.064
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 13.732
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.262
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.000