Project Number Date
test_Tails_ISO_stable 5109 22 Sep 2024, 12:34

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:36.455 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:2.231
Before features/support/hooks.rb:269 0.004
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.974
When I start Tails from USB drive "old" with network unplugged 1:25.961
Then the boot device has safe access rights 3.065
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:326 7.197
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.424
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:21.115
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 32.832
And I take note of which tps features are available 1.484
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.630
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.248
Before features/support/hooks.rb:269 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.642
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.170
When I write some files expected to persist 1.761
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.633
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 4.196
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.222
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.007
Tags: @product
2:24.866
Before features/support/hooks.rb:269 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 10.678
And I log in to a new session 18.567
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.487
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.876
Then the running Tails is installed on USB drive "to_upgrade" 16.439
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 2.372
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.484
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.377
Then all tps features from the old Tails version are active 1.574
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.138
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.377
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
6:25.836
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 12.499
And no SquashFS delta is installed 0.234
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.069
And Tor is ready 23.856
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.938
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.449
Given I shutdown Tails and wait for the computer to power off 8.715
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.832
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.171
And the file system changes introduced in version 6.2~testoverlayfs are present 0.352
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.304
When the network is plugged 0.074
And Tor is ready 17.252
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.571
Given I shutdown Tails and wait for the computer to power off 4.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.300
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.992
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.069
And Tor is ready 17.923
Then the Upgrader considers the system as up-to-date 0.311
# 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.357
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.008
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.364
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.833
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.819
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 20.832
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.439
After features/support/hooks.rb:326 0.595
After features/support/hooks.rb:100 0.000