Project Number Date
test_Tails_ISO_stable 5342 17 Dec 2024, 18:52

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 21:8.101 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:12.907
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.365
When I start Tails from USB drive "old" with network unplugged 1:36.589
Then the boot device has safe access rights 3.597
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 9.254
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.344
Before features/support/hooks.rb:269 0.007
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:29.440
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 30.115
And I take note of which tps features are available 2.006
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 8.369
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.372
Before features/support/hooks.rb:269 0.005
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.909
Then Tails is running from USB drive "old" 0.624
And all tps features are active 2.103
When I write some files expected to persist 2.044
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 3.314
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 4.762
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.151
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.202
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 10.857
And I log in to a new session 21.222
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.932
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.677
Then the running Tails is installed on USB drive "to_upgrade" 27.563
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:326 2.712
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.533
Before features/support/hooks.rb:269 0.013
Given a computer 1.410
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.362
Then all tps features from the old Tails version are active 1.844
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.540
And the expected persistent files created with the old Tails version are present in the filesystem 1.428
And all persistent directories from the old Tails version have safe access rights 2.578
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:53.495
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 22.358
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.749
When the network is plugged 0.313
And Tor is ready 23.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.507
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.377
Given I shutdown Tails and wait for the computer to power off 11.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.153
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.390
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# 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.407
When the network is plugged 0.084
And Tor is ready 19.039
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.119
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.979
Given I shutdown Tails and wait for the computer to power off 1:3.743
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.532
Then Tails is running version 6.3~testoverlayfs 0.089
And all tps features are active 5.772
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.364
When the network is plugged 0.492
And Tor is ready 16.714
Then the Upgrader considers the system as up-to-date 0.355
# 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.869
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.284
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
43.245
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 11.740
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.775
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 23.101
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.131
After features/support/hooks.rb:326 0.812
After features/support/hooks.rb:100 0.000