Project Number Date
test_Tails_ISO_stable 5427 28 Jan 2025, 15: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 21:21.951 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:3.470
Before features/support/hooks.rb:269 0.005
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.483
When I start Tails from USB drive "old" with network unplugged 1:26.219
Then the boot device has safe access rights 3.381
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.124
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.560
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.501
Before features/support/hooks.rb:269 0.007
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:27.992
Then Tails is running from USB drive "old" 0.415
And I create a persistent partition 33.969
And I take note of which tps features are available 2.114
Then a Tails persistence partition exists on USB drive "old" 1.019
And I shutdown Tails and wait for the computer to power off 6.772
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.013
Tags: @product
3:10.848
Before features/support/hooks.rb:269 0.008
Given a computer 0.291
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.897
Then Tails is running from USB drive "old" 0.808
And all tps features are active 2.463
When I write some files expected to persist 2.461
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.473
And all persistent directories from the old Tails version have safe access rights 2.869
And I take note of which tps features are available 0.600
And I shutdown Tails and wait for the computer to power off 4.531
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.208
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.669
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.224
And I log in to a new session 22.417
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.295
And I plug USB drive "to_upgrade" 2.610
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.816
Then the running Tails is installed on USB drive "to_upgrade" 21.823
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:326 3.103
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.599
Before features/support/hooks.rb:269 0.008
Given a computer 0.527
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.321
Then all tps features from the old Tails version are active 4.727
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 3.665
And the expected persistent files created with the old Tails version are present in the filesystem 1.505
And all persistent directories from the old Tails version have safe access rights 2.468
After features/support/hooks.rb:326 0.799
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:57.414
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 35.415
And no SquashFS delta is installed 0.128
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.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.174
And Tor is ready 25.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.169
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.359
Given I shutdown Tails and wait for the computer to power off 9.111
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.652
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 5.190
And the file system changes introduced in version 6.2~testoverlayfs are present 0.504
And only the 6.2~testoverlayfs SquashFS delta is installed 0.160
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.394
When the network is plugged 0.091
And Tor is ready 21.846
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.199
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.650
Given I shutdown Tails and wait for the computer to power off 6.685
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.523
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 4.991
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.271
When the network is plugged 0.096
And Tor is ready 48.395
Then the Upgrader considers the system as up-to-date 0.347
# 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.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.439
After features/support/hooks.rb:326 0.793
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.447
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.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 20.650
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.967
After features/support/hooks.rb:326 0.994
After features/support/hooks.rb:100 0.000