Project Number Date
test_Tails_ISO_stable 5265 15 Nov 2024, 08:51

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:0.358 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:23.164
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 34.205
When I start Tails from USB drive "old" with network unplugged 1:43.162
Then the boot device has safe access rights 3.373
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.529
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.475
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:27.197
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 34.867
And I take note of which tps features are available 1.584
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 8.401
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.967
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.545
Then Tails is running from USB drive "old" 0.551
And all tps features are active 2.008
When I write some files expected to persist 1.717
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.445
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 4.094
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.237
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.033
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.242
And I log in to a new session 20.619
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.910
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.244
Then the running Tails is installed on USB drive "to_upgrade" 20.119
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:326 7.411
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.578
Before features/support/hooks.rb:269 0.005
Given a computer 0.325
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.108
Then all tps features from the old Tails version are active 2.514
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.306
And the expected persistent files created with the old Tails version are present in the filesystem 1.419
And all persistent directories from the old Tails version have safe access rights 2.576
After features/support/hooks.rb:326 1.164
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
6:48.655
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 13.628
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.406
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.071
And Tor is ready 24.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.444
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.266
Given I shutdown Tails and wait for the computer to power off 9.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.060
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 2.282
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.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.408
# 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.335
When the network is plugged 0.089
And Tor is ready 20.942
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.153
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.292
Given I shutdown Tails and wait for the computer to power off 6.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.848
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.750
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.369
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.369
When the network is plugged 0.071
And Tor is ready 19.994
Then the Upgrader considers the system as up-to-date 0.372
# 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.650
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.350
After features/support/hooks.rb:326 0.834
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.482
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 10.495
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.051
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 21.130
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.347
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.000