Project Number Date
test_Tails_ISO_stable 5211 22 Oct 2024, 15:11

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 21:19.596 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:15.270
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 36.395
When I start Tails from USB drive "old" with network unplugged 1:33.533
Then the boot device has safe access rights 3.013
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 7.193
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.942
Before features/support/hooks.rb:269 0.006
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login 1:32.956
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 33.808
And I take note of which tps features are available 1.851
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.775
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.825
Before features/support/hooks.rb:269 0.007
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.806
Then Tails is running from USB drive "old" 1.505
And all tps features are active 2.180
When I write some files expected to persist 1.829
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 1.037
And all persistent directories from the old Tails version have safe access rights 3.728
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 4.481
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.201
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.019
Tags: @product
2:34.006
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.837
And I log in to a new session 20.165
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.017
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.433
Then the running Tails is installed on USB drive "to_upgrade" 22.619
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 7.501
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.043
Before features/support/hooks.rb:269 0.006
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.748
Then all tps features from the old Tails version are active 2.514
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 4.034
And the expected persistent files created with the old Tails version are present in the filesystem 1.555
And all persistent directories from the old Tails version have safe access rights 2.597
After features/support/hooks.rb:326 0.779
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:42.593
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 13.836
And no SquashFS delta is installed 0.234
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.456
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.546
When the network is plugged 0.088
And Tor is ready 20.226
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.379
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.372
Given I shutdown Tails and wait for the computer to power off 9.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.637
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.510
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.424
# 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.080
And Tor is ready 48.060
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.603
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.452
Given I shutdown Tails and wait for the computer to power off 56.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.556
Then Tails is running version 6.3~testoverlayfs 0.047
And all tps features are active 2.220
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.079
And Tor is ready 18.424
Then the Upgrader considers the system as up-to-date 0.370
# 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.700
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.949
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
1:2.915
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 11.971
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.522
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the signing key used by the Upgrader is outdated 1.062
But a current signing key is available on our website 0.000
When the network is plugged 0.134
And Tor is ready 48.523
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.592
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.000