Project Number Date
test_Tails_ISO_stable 5317 06 Dec 2024, 08:51

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:3.110 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:19.052
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 33.517
When I start Tails from USB drive "old" with network unplugged 1:39.829
Then the boot device has safe access rights 3.337
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.675
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.977
Before features/support/hooks.rb:269 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:25.972
Then Tails is running from USB drive "old" 0.404
And I create a persistent partition 32.103
And I take note of which tps features are available 1.894
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 8.495
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.723
Before features/support/hooks.rb:269 0.005
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.805
Then Tails is running from USB drive "old" 0.987
And all tps features are active 2.029
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.309
And all persistence configuration files have safe access rights 0.559
And all persistent directories from the old Tails version have safe access rights 3.019
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.256
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.251
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.435
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.168
And I log in to a new session 21.266
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.650
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.770
Then the running Tails is installed on USB drive "to_upgrade" 24.656
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:326 2.772
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.234
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.364
Then all tps features from the old Tails version are active 1.815
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.539
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.601
After features/support/hooks.rb:326 0.916
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:56.626
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.648
And no SquashFS delta is installed 0.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.064
And Tor is ready 25.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.453
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.884
Given I shutdown Tails and wait for the computer to power off 11.073
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.947
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.294
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.271
# 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.327
When the network is plugged 0.169
And Tor is ready 21.010
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.384
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.900
Given I shutdown Tails and wait for the computer to power off 4.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.681
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.100
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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.109
And Tor is ready 20.857
Then the Upgrader considers the system as up-to-date 0.336
# 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.399
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.074
After features/support/hooks.rb:326 0.936
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.060
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 12.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.918
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.287
After features/support/hooks.rb:326 1.355
After features/support/hooks.rb:100 0.000