Project Number Date
test_Tails_ISO_stable 4604 07 Jan 2024, 12:32

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 18:27.264 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
2:15.423
Before features/support/hooks.rb:245 0.006
Given a computer 0.907
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.199
And I write an old version of the Tails USB image to disk "old" 38.919
When I start Tails from USB drive "old" with network unplugged 1:30.064
Then the boot device has safe access rights 3.332
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:291 3.712
After features/support/hooks.rb:75 0.010
Tags: @product
2:5.985
Before features/support/hooks.rb:245 0.007
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:8.713
Then Tails is running from USB drive "old" 0.504
And I create a persistent partition 46.148
And I take note of which tps features are available 1.389
Then a Tails persistence partition exists on USB drive "old" 0.891
And I shutdown Tails and wait for the computer to power off 8.157
After features/support/hooks.rb:291 0.220
After features/support/hooks.rb:75 0.013
Tags: @product
2:37.136
Before features/support/hooks.rb:245 0.006
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:1.053
Then Tails is running from USB drive "old" 0.364
And all tps features are active 3.045
When I write some files expected to persist 2.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.747
And all persistent directories from the old Tails version have safe access rights 3.127
And I take note of which tps features are available 3.075
And I shutdown Tails and wait for the computer to power off 5.219
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.976
After features/support/hooks.rb:291 0.179
After features/support/hooks.rb:75 0.013
Tags: @product
2:40.517
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.757
And I log in to a new session 20.365
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.465
And I plug USB drive "to_upgrade" 2.650
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.633
Then the running Tails is installed on USB drive "to_upgrade" 13.260
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 0.958
After features/support/hooks.rb:75 0.000
Tags: @product
2:10.444
Before features/support/hooks.rb:245 0.007
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.661
Then all tps features from the old Tails version are active 1.737
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.679
And the expected persistent files created with the old Tails version are present in the filesystem 1.823
And all persistent directories from the old Tails version have safe access rights 2.944
After features/support/hooks.rb:291 0.720
After features/support/hooks.rb:75 0.010
6:8.186
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 13.286
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.371
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.070
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.377
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.635
When the network is plugged 0.036
And Tor is ready 18.684
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.944
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.901
Given I shutdown Tails and wait for the computer to power off 6.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.200
Then Tails is running version 2.2~testoverlayfsng 0.140
And all tps features are active 2.233
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.471
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.344
When the network is plugged 0.054
And Tor is ready 19.119
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.205
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.686
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.166
Then Tails is running version 2.3~testoverlayfsng 0.122
And all tps features are active 2.223
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.639
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.106
# 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.334
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.352
When the network is plugged 0.049
And Tor is ready 16.409
Then the Upgrader considers the system as up-to-date 0.296
# 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.848
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.675
After features/support/hooks.rb:291 0.904
After features/support/hooks.rb:75 0.020
29.570
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.373
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.353
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.079
And the signing key used by the Upgrader is outdated 1.528
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 16.444
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.694
After features/support/hooks.rb:291 1.272
After features/support/hooks.rb:75 0.000