Project Number Date
test_Tails_ISO_stable 5243 01 Nov 2024, 12:49

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:9.048 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:18.413
Before features/support/hooks.rb:269 0.008
Given a computer 0.284
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 31.907
When I start Tails from USB drive "old" with network unplugged 1:40.537
Then the boot device has safe access rights 3.458
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.101
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 7.282
After features/support/hooks.rb:100 0.010
Tags: @product
2:20.010
Before features/support/hooks.rb:269 0.009
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:34.224
Then Tails is running from USB drive "old" 0.424
And I create a persistent partition 34.359
And I take note of which tps features are available 1.631
Then a Tails persistence partition exists on USB drive "old" 0.784
And I shutdown Tails and wait for the computer to power off 8.347
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.462
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.330
Then Tails is running from USB drive "old" 0.607
And all tps features are active 2.189
When I write some files expected to persist 1.889
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.630
And all persistent directories from the old Tails version have safe access rights 2.721
And I take note of which tps features are available 0.539
And I shutdown Tails and wait for the computer to power off 4.595
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.505
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.357
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 11.822
And I log in to a new session 22.052
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.807
And I plug USB drive "to_upgrade" 2.470
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.020
Then the running Tails is installed on USB drive "to_upgrade" 21.734
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 7.412
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.762
Before features/support/hooks.rb:269 0.005
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.337
Then all tps features from the old Tails version are active 2.107
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.794
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 2.436
After features/support/hooks.rb:326 0.996
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:55.004
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 14.666
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.136
And Tor is ready 25.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.549
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.102
Given I shutdown Tails and wait for the computer to power off 14.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.733
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.649
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
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.345
# 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.260
When the network is plugged 0.089
And Tor is ready 20.164
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.114
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.979
Given I shutdown Tails and wait for the computer to power off 4.323
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.936
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 6.190
And the file system changes introduced in version 6.3~testoverlayfs are present 0.609
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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.416
When the network is plugged 0.470
And Tor is ready 19.589
Then the Upgrader considers the system as up-to-date 0.359
# 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.810
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.058
After features/support/hooks.rb:326 1.006
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
43.038
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 1.021
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 21.890
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.348
After features/support/hooks.rb:326 1.672
After features/support/hooks.rb:100 0.000