Project Number Date
test_Tails_ISO_stable 5197 18 Oct 2024, 12:38

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 19:29.964 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:16.948
Before features/support/hooks.rb:269 0.003
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 29.179
When I start Tails from USB drive "old" with network unplugged 1:42.235
Then the boot device has safe access rights 3.190
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 7.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.449
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:22.662
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 31.750
And I take note of which tps features are available 1.406
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.309
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.113
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.723
Then Tails is running from USB drive "old" 0.592
And all tps features are active 2.000
When I write some files expected to persist 2.464
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.446
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.957
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.215
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.668
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.414
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.080
And I log in to a new session 17.774
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.836
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.706
Then the running Tails is installed on USB drive "to_upgrade" 24.116
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 3.120
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.961
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.368
Then all tps features from the old Tails version are active 1.664
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.454
And the expected persistent files created with the old Tails version are present in the filesystem 1.500
And all persistent directories from the old Tails version have safe access rights 2.433
After features/support/hooks.rb:326 0.643
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:51.649
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 12.856
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.231
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.062
And Tor is ready 20.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.552
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.962
Given I shutdown Tails and wait for the computer to power off 8.527
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.407
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.387
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.262
When the network is plugged 0.074
And Tor is ready 17.547
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.661
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.549
Given I shutdown Tails and wait for the computer to power off 4.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.514
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.304
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.069
And Tor is ready 47.608
Then the Upgrader considers the system as up-to-date 0.326
# 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 13.764
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.198
After features/support/hooks.rb:326 0.729
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.427
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.462
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 1.670
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 20.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.394
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.000