Project Number Date
test_Tails_ISO_stable 4602 05 Jan 2024, 12:15

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:51.475 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:29.896
Before features/support/hooks.rb:245 0.006
Given a computer 0.937
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 20.693
When I start Tails from USB drive "old" with network unplugged 1:3.345
Then the boot device has safe access rights 2.964
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:291 3.487
After features/support/hooks.rb:75 0.008
Tags: @product
1:55.942
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 1:2.926
Then Tails is running from USB drive "old" 0.413
And I create a persistent partition 43.101
And I take note of which tps features are available 1.415
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 7.063
After features/support/hooks.rb:291 0.124
After features/support/hooks.rb:75 0.009
Tags: @product
2:13.947
Before features/support/hooks.rb:245 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:47.693
Then Tails is running from USB drive "old" 0.343
And all tps features are active 2.095
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.624
And all persistent directories from the old Tails version have safe access rights 2.754
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 3.088
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.719
After features/support/hooks.rb:291 0.109
After features/support/hooks.rb:75 0.007
Tags: @product
2:30.273
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.978
And I log in to a new session 15.667
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.187
And I plug USB drive "to_upgrade" 2.461
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.320
Then the running Tails is installed on USB drive "to_upgrade" 12.232
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:291 1.302
After features/support/hooks.rb:75 0.000
Tags: @product
2:7.010
Before features/support/hooks.rb:245 0.012
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.122
Then all tps features from the old Tails version are active 1.930
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.900
And the expected persistent files created with the old Tails version are present in the filesystem 1.789
And all persistent directories from the old Tails version have safe access rights 2.666
After features/support/hooks.rb:291 0.543
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:4.360
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.679
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.263
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.041
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.373
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.619
When the network is plugged 0.038
And Tor is ready 16.266
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.937
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.489
Given I shutdown Tails and wait for the computer to power off 6.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.056
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 2.304
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.442
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.256
# 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.382
When the network is plugged 0.032
And Tor is ready 16.868
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.623
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.994
Given I shutdown Tails and wait for the computer to power off 4.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.692
Then Tails is running version 2.3~testoverlayfsng 0.101
And all tps features are active 2.219
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.565
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.262
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.291
When the network is plugged 0.108
And Tor is ready 14.923
Then the Upgrader considers the system as up-to-date 0.319
# 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 24.899
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.343
After features/support/hooks.rb:291 0.830
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
30.043
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 9.774
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.286
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.070
And the signing key used by the Upgrader is outdated 1.675
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 15.155
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.035
After features/support/hooks.rb:291 1.373
After features/support/hooks.rb:75 0.000