Project Number Date
test_Tails_ISO_stable 5424 28 Jan 2025, 02:43

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:55.126 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:0.700
Before features/support/hooks.rb:269 0.005
Given a computer 0.234
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" 29.406
When I start Tails from USB drive "old" with network unplugged 1:25.826
Then the boot device has safe access rights 3.128
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.540
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:23.228
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 31.672
And I take note of which tps features are available 1.516
Then a Tails persistence partition exists on USB drive "old" 0.856
And I shutdown Tails and wait for the computer to power off 8.724
After features/support/hooks.rb:326 0.208
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.146
Before features/support/hooks.rb:269 0.005
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.277
Then Tails is running from USB drive "old" 1.503
And all tps features are active 1.881
When I write some files expected to persist 1.712
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 3.662
And I take note of which tps features are available 0.564
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.352
After features/support/hooks.rb:326 0.112
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.553
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.395
And I log in to a new session 19.565
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.702
And I plug USB drive "to_upgrade" 2.350
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.614
Then the running Tails is installed on USB drive "to_upgrade" 21.456
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:326 2.541
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.349
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.180
Then all tps features from the old Tails version are active 1.648
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.722
And the expected persistent files created with the old Tails version are present in the filesystem 1.696
And all persistent directories from the old Tails version have safe access rights 2.566
After features/support/hooks.rb:326 0.913
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:29.430
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 11.948
And no SquashFS delta is installed 0.225
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
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.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.697
When the network is plugged 0.099
And Tor is ready 19.225
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.477
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.150
Given I shutdown Tails and wait for the computer to power off 8.859
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.391
Then Tails is running version 6.2~testoverlayfs 0.031
And all tps features are active 2.474
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.083
And Tor is ready 21.044
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.370
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.109
Given I shutdown Tails and wait for the computer to power off 4.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.236
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.143
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.079
And Tor is ready 19.251
Then the Upgrader considers the system as up-to-date 0.346
# 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.708
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.982
After features/support/hooks.rb:326 0.700
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.405
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.953
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.788
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 20.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.709
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.000