Project Number Date
test_Tails_ISO_stable 5009 07 Aug 2024, 20:40

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 19:47.302 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:20.721
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.452
When I start Tails from USB drive "old" with network unplugged 1:43.955
Then the boot device has safe access rights 3.020
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.198
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.022
Before features/support/hooks.rb:269 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:21.040
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 32.578
And I take note of which tps features are available 1.605
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.495
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.050
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.681
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.028
When I write some files expected to persist 1.911
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.472
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.367
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.977
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.630
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.533
And I log in to a new session 20.166
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.838
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.871
Then the running Tails is installed on USB drive "to_upgrade" 21.339
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.222
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.531
Before features/support/hooks.rb:269 0.007
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.545
Then all tps features from the old Tails version are active 1.623
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.623
And the expected persistent files created with the old Tails version are present in the filesystem 1.616
And all persistent directories from the old Tails version have safe access rights 2.594
After features/support/hooks.rb:326 0.610
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:59.144
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 40.302
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.077
And Tor is ready 47.620
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.602
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.900
Given I shutdown Tails and wait for the computer to power off 9.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.016
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.123
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.291
When the network is plugged 0.069
And Tor is ready 19.669
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.409
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.397
Given I shutdown Tails and wait for the computer to power off 4.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.371
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.107
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.059
And Tor is ready 17.495
Then the Upgrader considers the system as up-to-date 0.275
# 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 14.581
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
38.201
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 9.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
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 0.929
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 20.666
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.564
After features/support/hooks.rb:326 0.888
After features/support/hooks.rb:100 0.000