Project Number Date
test_Tails_ISO_stable 4814 28 Apr 2024, 12:25

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:8.373 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:13.233
Before features/support/hooks.rb:259 0.006
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 34.291
When I start Tails from USB drive "old" with network unplugged 1:33.340
Then the boot device has safe access rights 3.193
And Tails is running from USB drive "old" 0.397
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.115
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:305 3.538
After features/support/hooks.rb:89 0.009
Tags: @product
2:14.747
Before features/support/hooks.rb:259 0.004
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login 1:26.238
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 36.594
And I take note of which tps features are available 1.976
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.529
After features/support/hooks.rb:305 0.229
After features/support/hooks.rb:89 0.009
Tags: @product
2:42.589
Before features/support/hooks.rb:259 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.881
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.119
When I write some files expected to persist 1.842
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.761
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.409
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.852
After features/support/hooks.rb:305 0.146
After features/support/hooks.rb:89 0.010
Tags: @product
2:23.979
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.050
And I log in to a new session 17.122
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.317
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.090
Then the running Tails is installed on USB drive "to_upgrade" 17.619
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:305 6.746
After features/support/hooks.rb:89 0.000
Tags: @product
2:19.527
Before features/support/hooks.rb:259 0.008
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.874
Then all tps features from the old Tails version are active 2.266
And Tails is running from USB drive "to_upgrade" 0.615
And the boot device has safe access rights 3.212
And the expected persistent files created with the old Tails version are present in the filesystem 1.887
And all persistent directories from the old Tails version have safe access rights 2.461
After features/support/hooks.rb:305 0.700
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
7:39.824
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.269
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.045
And Tor is ready 18.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.902
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.206
Given I shutdown Tails and wait for the computer to power off 1:22.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.397
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.178
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.107
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.263
When the network is plugged 0.113
And Tor is ready 18.768
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.843
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.570
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.267
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.985
And the file system changes introduced in version 6.3~testoverlayfs are present 0.584
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.281
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.044
And Tor is ready 18.702
Then the Upgrader considers the system as up-to-date 0.322
# 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.080
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.898
After features/support/hooks.rb:305 0.771
After features/support/hooks.rb:89 0.016
Tags: @product @automatic_upgrade
34.470
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.558
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 17.199
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.656
After features/support/hooks.rb:305 0.763
After features/support/hooks.rb:89 0.000