Project Number Date
test_Tails_ISO_stable 4641 26 Jan 2024, 13: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.708 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:44.471
Before features/support/hooks.rb:245 0.006
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 20.456
When I start Tails from USB drive "old" with network unplugged 1:18.597
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:291 3.723
After features/support/hooks.rb:75 0.011
Tags: @product
1:56.120
Before features/support/hooks.rb:245 0.006
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login 1:3.708
Then Tails is running from USB drive "old" 0.468
And I create a persistent partition 42.412
And I take note of which tps features are available 1.438
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 7.065
After features/support/hooks.rb:291 0.154
After features/support/hooks.rb:75 0.010
Tags: @product
2:18.678
Before features/support/hooks.rb:245 0.006
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.835
Then Tails is running from USB drive "old" 0.361
And all tps features are active 2.118
When I write some files expected to persist 2.062
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.277
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 3.046
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 3.061
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.783
After features/support/hooks.rb:291 0.138
After features/support/hooks.rb:75 0.010
Tags: @product
2:35.227
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.880
And I log in to a new session 20.150
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.095
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.065
Then the running Tails is installed on USB drive "to_upgrade" 13.150
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 0.857
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.267
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:50.498
Then all tps features from the old Tails version are active 1.572
And Tails is running from USB drive "to_upgrade" 0.427
And the boot device has safe access rights 3.871
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 3.065
After features/support/hooks.rb:291 0.738
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:47.219
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.925
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.270
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.078
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.340
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.584
When the network is plugged 0.029
And Tor is ready 15.980
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.798
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.007
Given I shutdown Tails and wait for the computer to power off 6.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.297
Then Tails is running version 2.2~testoverlayfsng 0.116
And all tps features are active 2.698
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.643
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.283
When the network is plugged 0.041
And Tor is ready 14.777
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.665
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.081
Given I shutdown Tails and wait for the computer to power off 4.368
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.566
Then Tails is running version 2.3~testoverlayfsng 0.107
And all tps features are active 2.116
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.606
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.069
# 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.288
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.349
When the network is plugged 0.033
And Tor is ready 14.876
Then the Upgrader considers the system as up-to-date 0.248
# 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 27.804
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.221
After features/support/hooks.rb:291 0.919
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
28.723
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 10.030
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.335
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.216
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 14.294
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.728
After features/support/hooks.rb:291 0.699
After features/support/hooks.rb:75 0.000