Project Number Date
test_Tails_ISO_stable 5185 16 Oct 2024, 08:53

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:54.899 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:23.199
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.094
When I start Tails from USB drive "old" with network unplugged 1:47.449
Then the boot device has safe access rights 3.279
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:326 3.560
After features/support/hooks.rb:100 0.012
Tags: @product
2:8.888
Before features/support/hooks.rb:269 0.007
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:24.073
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 32.869
And I take note of which tps features are available 1.940
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.613
After features/support/hooks.rb:326 0.221
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.638
Before features/support/hooks.rb:269 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.190
Then Tails is running from USB drive "old" 0.542
And all tps features are active 2.143
When I write some files expected to persist 1.775
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 3.908
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.364
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.292
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.012
Tags: @product
2:43.940
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.601
And I log in to a new session 19.232
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.751
And I plug USB drive "to_upgrade" 2.440
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.659
Then the running Tails is installed on USB drive "to_upgrade" 24.843
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.713
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.829
Before features/support/hooks.rb:269 0.007
Given a computer 0.264
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.433
Then all tps features from the old Tails version are active 1.885
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.174
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 2.332
After features/support/hooks.rb:326 0.814
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:54.342
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 25.592
And no SquashFS delta is installed 0.439
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.897
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.067
When the network is plugged 0.128
And Tor is ready 22.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.193
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.963
Given I shutdown Tails and wait for the computer to power off 14.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.719
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 2.629
And the file system changes introduced in version 6.2~testoverlayfs are present 0.433
And only the 6.2~testoverlayfs SquashFS delta is installed 0.105
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.607
# 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.315
When the network is plugged 0.109
And Tor is ready 18.084
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.918
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.885
Given I shutdown Tails and wait for the computer to power off 4.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.247
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.410
And the file system changes introduced in version 6.3~testoverlayfs are present 0.610
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.075
And Tor is ready 18.128
Then the Upgrader considers the system as up-to-date 0.348
# 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.763
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.319
After features/support/hooks.rb:326 0.922
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
37.061
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.978
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.488
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.336
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 17.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.111
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.000