Project Number Date
test_Tails_ISO_stable 5438 02 Feb 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:0.541 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:54.439
Before features/support/hooks.rb:269 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.483
When I start Tails from USB drive "old" with network unplugged 1:18.973
Then the boot device has safe access rights 2.773
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 6.796
After features/support/hooks.rb:100 0.008
Tags: @product
1:59.640
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:20.129
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 30.793
And I take note of which tps features are available 1.286
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 6.163
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.008
Tags: @product
2:43.752
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.492
Then Tails is running from USB drive "old" 0.546
And all tps features are active 1.945
When I write some files expected to persist 1.623
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.523
And I take note of which tps features are available 0.409
And I shutdown Tails and wait for the computer to power off 4.251
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.170
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.000
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 9.570
And I log in to a new session 18.707
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.509
And I plug USB drive "to_upgrade" 2.331
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.561
Then the running Tails is installed on USB drive "to_upgrade" 17.885
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.362
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.486
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.806
Then all tps features from the old Tails version are active 1.964
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.389
And all persistent directories from the old Tails version have safe access rights 2.271
After features/support/hooks.rb:326 0.573
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:9.779
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.078
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.073
And Tor is ready 20.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.821
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.197
Given I shutdown Tails and wait for the computer to power off 8.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.370
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.175
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.290
# 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.276
When the network is plugged 0.098
And Tor is ready 20.295
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.333
Given I shutdown Tails and wait for the computer to power off 4.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.122
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.259
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.063
And Tor is ready 20.448
Then the Upgrader considers the system as up-to-date 0.309
# 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.681
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.248
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
35.441
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 10.677
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.624
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.621
And Tor is ready 18.293
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.076
After features/support/hooks.rb:326 1.242
After features/support/hooks.rb:100 0.000