Project Number Date
test_Tails_ISO_stable 5391 14 Jan 2025, 12:27

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 18:53.359 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
1:56.783
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.412
When I start Tails from USB drive "old" with network unplugged 1:22.227
Then the boot device has safe access rights 2.959
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 7.045
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.911
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:23.965
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 31.587
And I take note of which tps features are available 1.502
Then a Tails persistence partition exists on USB drive "old" 0.757
And I shutdown Tails and wait for the computer to power off 8.599
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.007
Tags: @product
2:54.362
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.233
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.001
When I write some files expected to persist 1.905
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.395
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.319
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.935
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.371
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 10.272
And I log in to a new session 17.158
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.439
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.031
Then the running Tails is installed on USB drive "to_upgrade" 19.632
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.563
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.911
Before features/support/hooks.rb:269 0.005
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.018
Then all tps features from the old Tails version are active 1.580
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 2.964
And the expected persistent files created with the old Tails version are present in the filesystem 1.477
And all persistent directories from the old Tails version have safe access rights 2.344
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.696
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.126
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.088
And Tor is ready 21.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.097
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.005
Given I shutdown Tails and wait for the computer to power off 8.410
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.108
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.068
And the file system changes introduced in version 6.2~testoverlayfs are present 0.281
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.339
When the network is plugged 0.117
And Tor is ready 18.805
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.421
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.341
Given I shutdown Tails and wait for the computer to power off 4.368
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.556
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.016
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.285
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.081
And Tor is ready 46.807
Then the Upgrader considers the system as up-to-date 0.318
# 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.895
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.013
After features/support/hooks.rb:326 0.813
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.323
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.541
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 21.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.961
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.000