Project Number Date
test_Tails_ISO_stable 4633 24 Jan 2024, 16:22

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:57.909 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:49.747
Before features/support/hooks.rb:245 0.006
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.091
And I write an old version of the Tails USB image to disk "old" 21.830
When I start Tails from USB drive "old" with network unplugged 1:22.264
Then the boot device has safe access rights 3.248
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.250
After features/support/hooks.rb:291 3.857
After features/support/hooks.rb:75 0.009
Tags: @product
2:3.148
Before features/support/hooks.rb:245 0.006
Given a computer 0.827
And I start Tails from USB drive "old" with network unplugged and I login 1:6.449
Then Tails is running from USB drive "old" 0.531
And I create a persistent partition 43.932
And I take note of which tps features are available 2.290
Then a Tails persistence partition exists on USB drive "old" 0.969
And I shutdown Tails and wait for the computer to power off 8.147
After features/support/hooks.rb:291 0.165
After features/support/hooks.rb:75 0.010
Tags: @product
2:21.834
Before features/support/hooks.rb:245 0.006
Given a computer 0.667
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:54.648
Then Tails is running from USB drive "old" 0.452
And all tps features are active 2.289
When I write some files expected to persist 1.812
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.732
And I take note of which tps features are available 0.450
And I shutdown Tails and wait for the computer to power off 3.078
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.032
After features/support/hooks.rb:291 0.093
After features/support/hooks.rb:75 0.009
Tags: @product
2:32.840
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 10.065
And I log in to a new session 16.449
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.225
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.018
Then the running Tails is installed on USB drive "to_upgrade" 13.165
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:291 0.914
After features/support/hooks.rb:75 0.000
Tags: @product
2:10.485
Before features/support/hooks.rb:245 0.007
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.084
Then all tps features from the old Tails version are active 2.064
And Tails is running from USB drive "to_upgrade" 0.447
And the boot device has safe access rights 4.297
And the expected persistent files created with the old Tails version are present in the filesystem 1.578
And all persistent directories from the old Tails version have safe access rights 2.797
After features/support/hooks.rb:291 0.896
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:29.142
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.755
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.284
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.426
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.619
When the network is plugged 0.033
And Tor is ready 46.757
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.624
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 11.507
Given I shutdown Tails and wait for the computer to power off 7.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.130
Then Tails is running version 2.2~testoverlayfsng 0.121
And all tps features are active 2.239
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.414
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.123
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.299
When the network is plugged 0.046
And Tor is ready 16.274
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.085
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.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.322
Then Tails is running version 2.3~testoverlayfsng 0.189
And all tps features are active 2.069
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.579
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.075
# 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.340
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.448
When the network is plugged 0.044
And Tor is ready 16.396
Then the Upgrader considers the system as up-to-date 0.328
# 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 25.201
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.378
After features/support/hooks.rb:291 0.825
After features/support/hooks.rb:75 0.038
Tags: @product @automatic_upgrade
30.710
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.011
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.326
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.072
And the signing key used by the Upgrader is outdated 1.225
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 14.421
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.605
After features/support/hooks.rb:291 1.074
After features/support/hooks.rb:75 0.000