Project Number Date
test_Tails_ISO_stable 5126 30 Sep 2024, 12:52

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 20:40.061 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:40.901
Before features/support/hooks.rb:269 0.008
Given a computer 0.284
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.074
And I write an old version of the Tails USB image to disk "old" 55.171
When I start Tails from USB drive "old" with network unplugged 1:40.442
Then the boot device has safe access rights 2.949
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:326 7.104
After features/support/hooks.rb:100 0.017
Tags: @product
2:24.961
Before features/support/hooks.rb:269 0.005
Given a computer 1.518
And I start Tails from USB drive "old" with network unplugged and I login 1:32.331
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 39.881
And I take note of which tps features are available 1.645
Then a Tails persistence partition exists on USB drive "old" 0.851
And I shutdown Tails and wait for the computer to power off 8.393
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.016
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.793
Then Tails is running from USB drive "old" 0.328
And all tps features are active 2.083
When I write some files expected to persist 1.830
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
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.382
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.020
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.879
Before features/support/hooks.rb:269 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.929
And I log in to a new session 17.748
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.515
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.117
Then the running Tails is installed on USB drive "to_upgrade" 17.753
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 2.424
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.470
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.139
Then all tps features from the old Tails version are active 1.566
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.359
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:41.366
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.718
And no SquashFS delta is installed 0.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.093
And Tor is ready 19.205
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.595
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.601
Given I shutdown Tails and wait for the computer to power off 1:14.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.057
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.065
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.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 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.093
And Tor is ready 47.250
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.575
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.888
Given I shutdown Tails and wait for the computer to power off 4.208
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.108
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.029
And the file system changes introduced in version 6.3~testoverlayfs are present 0.439
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.144
And Tor is ready 18.795
Then the Upgrader considers the system as up-to-date 0.325
# 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 13.467
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.241
After features/support/hooks.rb:326 0.739
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.464
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.801
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.782
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 15.995
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.340
After features/support/hooks.rb:326 0.851
After features/support/hooks.rb:100 0.000