Project Number Date
test_Tails_ISO_stable 4585 22 Dec 2023, 12:46

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:7.632 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:25.540
Before features/support/hooks.rb:245 0.007
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 21.030
When I start Tails from USB drive "old" with network unplugged 59.210
Then the boot device has safe access rights 3.104
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:291 3.517
After features/support/hooks.rb:75 0.026
Tags: @product
1:58.122
Before features/support/hooks.rb:245 0.005
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login 1:4.403
Then Tails is running from USB drive "old" 0.425
And I create a persistent partition 41.877
And I take note of which tps features are available 1.585
Then a Tails persistence partition exists on USB drive "old" 1.246
And I shutdown Tails and wait for the computer to power off 8.324
After features/support/hooks.rb:291 0.227
After features/support/hooks.rb:75 0.011
Tags: @product
2:22.356
Before features/support/hooks.rb:245 0.025
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.716
Then Tails is running from USB drive "old" 0.433
And all tps features are active 2.223
When I write some files expected to persist 1.918
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.315
And all persistence configuration files have safe access rights 0.751
And all persistent directories from the old Tails version have safe access rights 2.669
And I take note of which tps features are available 0.545
And I shutdown Tails and wait for the computer to power off 4.187
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.410
After features/support/hooks.rb:291 0.123
After features/support/hooks.rb:75 0.009
Tags: @product
2:33.709
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 11.059
And I log in to a new session 15.450
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.341
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.019
Then the running Tails is installed on USB drive "to_upgrade" 14.006
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:291 1.904
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.711
Before features/support/hooks.rb:245 0.006
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.403
Then all tps features from the old Tails version are active 1.674
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.445
And the expected persistent files created with the old Tails version are present in the filesystem 1.655
And all persistent directories from the old Tails version have safe access rights 2.951
After features/support/hooks.rb:291 0.627
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:9.882
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 10.863
And no SquashFS delta is installed 0.794
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.292
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.092
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.471
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.603
When the network is plugged 0.066
And Tor is ready 17.751
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.683
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.287
Given I shutdown Tails and wait for the computer to power off 6.713
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.085
Then Tails is running version 2.2~testoverlayfsng 0.102
And all tps features are active 2.327
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.394
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.323
When the network is plugged 0.042
And Tor is ready 15.991
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.656
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.365
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.407
Then Tails is running version 2.3~testoverlayfsng 0.110
And all tps features are active 2.257
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.534
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.054
# 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.244
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.271
When the network is plugged 0.047
And Tor is ready 13.713
Then the Upgrader considers the system as up-to-date 10.774
# 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.428
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.526
After features/support/hooks.rb:291 0.696
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
32.309
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.774
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.288
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the signing key used by the Upgrader is outdated 1.809
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 15.631
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.693
After features/support/hooks.rb:291 1.276
After features/support/hooks.rb:75 0.000