Project Number Date
test_Tails_ISO_stable 5113 24 Sep 2024, 08: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 20:22.346 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:16.997
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.063
When I start Tails from USB drive "old" with network unplugged 1:38.431
Then the boot device has safe access rights 3.196
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 3.717
After features/support/hooks.rb:100 0.014
Tags: @product
2:11.759
Before features/support/hooks.rb:269 0.006
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login 1:28.825
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 31.208
And I take note of which tps features are available 1.850
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.439
After features/support/hooks.rb:326 0.202
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.224
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.089
Then Tails is running from USB drive "old" 0.341
And all tps features are active 2.128
When I write some files expected to persist 2.101
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.354
And all persistence configuration files have safe access rights 0.550
And all persistent directories from the old Tails version have safe access rights 2.637
And I take note of which tps features are available 0.614
And I shutdown Tails and wait for the computer to power off 4.137
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.081
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.010
Tags: @product
2:45.463
Before features/support/hooks.rb:269 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 13.827
And I log in to a new session 21.482
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.079
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.443
Then the running Tails is installed on USB drive "to_upgrade" 24.652
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.294
After features/support/hooks.rb:326 3.594
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.008
Before features/support/hooks.rb:269 0.016
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.198
Then all tps features from the old Tails version are active 4.062
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.139
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.545
After features/support/hooks.rb:326 1.229
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:6.908
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.057
And no SquashFS delta is installed 0.502
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.693
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.861
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.566
When the network is plugged 0.079
And Tor is ready 22.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.836
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.850
Given I shutdown Tails and wait for the computer to power off 11.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.544
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.383
# 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.261
When the network is plugged 0.068
And Tor is ready 17.195
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.846
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.751
Given I shutdown Tails and wait for the computer to power off 6.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.506
Then Tails is running version 6.3~testoverlayfs 0.049
And all tps features are active 2.391
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.375
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.083
And Tor is ready 21.033
Then the Upgrader considers the system as up-to-date 0.332
# 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 15.457
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.142
After features/support/hooks.rb:326 0.679
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.985
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.894
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.148
And the signing key used by the Upgrader is outdated 0.852
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 21.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.136
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.000