Project Number Date
test_Tails_ISO_stable 5261 13 Nov 2024, 08:48

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:51.865 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:9.163
Before features/support/hooks.rb:269 0.005
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.193
When I start Tails from USB drive "old" with network unplugged 1:33.210
Then the boot device has safe access rights 3.378
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 7.144
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.415
Before features/support/hooks.rb:269 0.005
Given a computer 0.358
And I start Tails from USB drive "old" with network unplugged and I login 1:28.016
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 37.031
And I take note of which tps features are available 1.804
Then a Tails persistence partition exists on USB drive "old" 0.925
And I shutdown Tails and wait for the computer to power off 8.924
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.008
Tags: @product
3:5.286
Before features/support/hooks.rb:269 0.006
Given a computer 0.293
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.663
Then Tails is running from USB drive "old" 1.641
And all tps features are active 2.505
When I write some files expected to persist 3.173
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 3.209
And I take note of which tps features are available 0.541
And I shutdown Tails and wait for the computer to power off 4.067
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.518
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.329
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.932
And I log in to a new session 20.513
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.133
And I plug USB drive "to_upgrade" 2.505
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.471
Then the running Tails is installed on USB drive "to_upgrade" 26.264
And I unplug USB drive "to_upgrade" 0.261
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:326 2.270
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.578
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.388
Then all tps features from the old Tails version are active 1.935
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 4.077
And the expected persistent files created with the old Tails version are present in the filesystem 1.620
And all persistent directories from the old Tails version have safe access rights 2.947
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:27.494
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.669
And no SquashFS delta is installed 0.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.357
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.088
And Tor is ready 22.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.783
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.736
Given I shutdown Tails and wait for the computer to power off 11.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.151
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.321
And the file system changes introduced in version 6.2~testoverlayfs are present 0.408
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.392
When the network is plugged 0.085
And Tor is ready 23.847
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.968
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.973
Given I shutdown Tails and wait for the computer to power off 4.673
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.832
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 3.569
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.079
And Tor is ready 19.557
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.586
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.051
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
47.597
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 15.636
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.089
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.831
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 20.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.519
After features/support/hooks.rb:326 1.751
After features/support/hooks.rb:100 0.000