Project Number Date
test_Tails_ISO_stable 5385 10 Jan 2025, 12:40

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:51.464 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:55.042
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.762
When I start Tails from USB drive "old" with network unplugged 1:18.901
Then the boot device has safe access rights 3.101
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.590
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.653
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 1:22.064
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 32.770
And I take note of which tps features are available 1.265
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.235
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.119
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.215
Then Tails is running from USB drive "old" 0.321
And all tps features are active 2.210
When I write some files expected to persist 1.820
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.604
And I take note of which tps features are available 0.572
And I shutdown Tails and wait for the computer to power off 4.187
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.369
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.007
Tags: @product
2:46.528
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.355
And I log in to a new session 19.309
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.600
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.611
Then the running Tails is installed on USB drive "to_upgrade" 25.804
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.896
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.419
Before features/support/hooks.rb:269 0.004
Given a computer 0.255
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.185
Then all tps features from the old Tails version are active 1.821
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.150
And the expected persistent files created with the old Tails version are present in the filesystem 1.349
And all persistent directories from the old Tails version have safe access rights 2.314
After features/support/hooks.rb:326 0.805
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
6:21.518
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 27.220
And no SquashFS delta is installed 0.258
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.121
And Tor is ready 21.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.544
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.636
Given I shutdown Tails and wait for the computer to power off 8.933
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.524
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.429
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.265
When the network is plugged 0.100
And Tor is ready 17.755
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.411
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.558
Given I shutdown Tails and wait for the computer to power off 4.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.622
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.455
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.400
And Tor is ready 16.132
Then the Upgrader considers the system as up-to-date 0.311
# 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.972
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.922
After features/support/hooks.rb:326 0.668
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
35.182
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 9.848
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.088
But a current signing key is available on our website 0.000
When the network is plugged 0.147
And Tor is ready 19.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.933
After features/support/hooks.rb:326 1.289
After features/support/hooks.rb:100 0.000