Project Number Date
test_Tails_ISO_devel 3236 14 Jan 2024, 12:34

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:1.262 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:26.050
Before features/support/hooks.rb:245 0.009
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 19.356
When I start Tails from USB drive "old" with network unplugged 1:1.524
Then the boot device has safe access rights 3.005
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:291 3.616
After features/support/hooks.rb:75 0.014
Tags: @product
1:59.635
Before features/support/hooks.rb:245 0.009
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:4.246
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 45.285
And I take note of which tps features are available 1.588
Then a Tails persistence partition exists on USB drive "old" 0.884
And I shutdown Tails and wait for the computer to power off 7.096
After features/support/hooks.rb:291 0.130
After features/support/hooks.rb:75 0.015
Tags: @product
2:24.219
Before features/support/hooks.rb:245 0.007
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:54.267
Then Tails is running from USB drive "old" 0.344
And all tps features are active 2.225
When I write some files expected to persist 2.086
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.771
And all persistent directories from the old Tails version have safe access rights 2.879
And I take note of which tps features are available 0.442
And I shutdown Tails and wait for the computer to power off 5.065
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.649
After features/support/hooks.rb:291 0.120
After features/support/hooks.rb:75 0.009
Tags: @product
2:33.874
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 10.788
And I log in to a new session 15.955
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.262
And I plug USB drive "to_upgrade" 2.807
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.811
Then the running Tails is installed on USB drive "to_upgrade" 13.837
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:291 6.720
After features/support/hooks.rb:75 0.000
Tags: @product
1:58.918
Before features/support/hooks.rb:245 0.008
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.103
Then all tps features from the old Tails version are active 1.650
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.415
And the expected persistent files created with the old Tails version are present in the filesystem 1.559
And all persistent directories from the old Tails version have safe access rights 2.647
After features/support/hooks.rb:291 0.759
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:9.274
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 11.224
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.285
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.057
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.414
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.567
When the network is plugged 0.052
And Tor is ready 17.226
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.003
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.838
Given I shutdown Tails and wait for the computer to power off 9.804
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.737
Then Tails is running version 2.2~testoverlayfsng 0.134
And all tps features are active 2.295
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.370
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.317
When the network is plugged 0.046
And Tor is ready 15.875
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.771
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.761
Given I shutdown Tails and wait for the computer to power off 4.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.430
Then Tails is running version 2.3~testoverlayfsng 0.129
And all tps features are active 2.248
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.673
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.084
# 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.286
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.333
When the network is plugged 0.039
And Tor is ready 16.286
Then the Upgrader considers the system as up-to-date 10.810
# 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.923
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.356
After features/support/hooks.rb:291 0.997
After features/support/hooks.rb:75 0.029
Tags: @product @automatic_upgrade
29.288
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.529
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.464
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the signing key used by the Upgrader is outdated 0.579
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 15.792
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.802
After features/support/hooks.rb:291 0.914
After features/support/hooks.rb:75 0.000