Project Number Date
test_Tails_ISO_stable 5277 19 Nov 2024, 08:44

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:53.945 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:29.977
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 32.031
When I start Tails from USB drive "old" with network unplugged 1:52.555
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 3.686
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.432
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:25.338
Then Tails is running from USB drive "old" 0.391
And I create a persistent partition 33.310
And I take note of which tps features are available 1.528
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.844
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.765
Before features/support/hooks.rb:269 0.004
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.424
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.313
When I write some files expected to persist 1.830
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.593
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 4.212
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.647
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.170
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.249
And I log in to a new session 19.550
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.695
And I plug USB drive "to_upgrade" 2.350
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.155
Then the running Tails is installed on USB drive "to_upgrade" 18.755
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 3.393
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.848
Before features/support/hooks.rb:269 0.005
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.937
Then all tps features from the old Tails version are active 1.571
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.627
And the expected persistent files created with the old Tails version are present in the filesystem 1.534
And all persistent directories from the old Tails version have safe access rights 2.555
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:43.116
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 12.493
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.565
When the network is plugged 0.070
And Tor is ready 22.314
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.850
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.229
Given I shutdown Tails and wait for the computer to power off 9.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.676
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.343
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.284
When the network is plugged 0.115
And Tor is ready 20.282
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.137
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.598
Given I shutdown Tails and wait for the computer to power off 4.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.632
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.198
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.078
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.078
And Tor is ready 15.979
Then the Upgrader considers the system as up-to-date 10.931
# 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.823
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.015
After features/support/hooks.rb:326 0.946
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
42.634
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 11.499
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 1.090
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 25.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.811
After features/support/hooks.rb:326 0.667
After features/support/hooks.rb:100 0.000