Project Number Date
test_Tails_ISO_devel 3461 13 Jul 2024, 12:43

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 17:57.778 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:7.907
Before features/support/hooks.rb:269 0.007
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 31.131
When I start Tails from USB drive "old" with network unplugged 1:31.647
Then the boot device has safe access rights 2.867
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 9.035
After features/support/hooks.rb:100 0.010
Tags: @product
2:0.144
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:18.305
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 30.404
And I take note of which tps features are available 1.736
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.350
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.610
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.354
Then Tails is running from USB drive "old" 0.346
And all tps features are active 2.115
When I write some files expected to persist 1.629
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.443
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.318
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.115
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.138
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.027
And I log in to a new session 18.910
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.266
And I plug USB drive "to_upgrade" 2.342
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.907
Then the running Tails is installed on USB drive "to_upgrade" 18.256
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 2.224
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.367
Before features/support/hooks.rb:269 0.008
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.293
Then all tps features from the old Tails version are active 1.534
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.173
And the expected persistent files created with the old Tails version are present in the filesystem 1.527
And all persistent directories from the old Tails version have safe access rights 2.315
After features/support/hooks.rb:326 0.858
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
5:59.823
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 11.534
And no SquashFS delta is installed 1.004
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.066
And Tor is ready 21.441
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.339
Given I shutdown Tails and wait for the computer to power off 8.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.672
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.071
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.281
When the network is plugged 0.045
And Tor is ready 19.328
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.371
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.757
Given I shutdown Tails and wait for the computer to power off 4.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.432
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.160
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.392
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.053
And Tor is ready 18.121
Then the Upgrader considers the system as up-to-date 0.320
# 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.318
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.132
After features/support/hooks.rb:326 0.855
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.786
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 9.702
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.881
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 17.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.318
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.000