Project Number Date
test_Tails_ISO_devel 3792 29 Apr 2025, 13:13

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 23:5.991 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
3:4.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.324
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 57.572
When I start Tails from USB drive "old" with network unplugged 2:0.795
Then the boot device has safe access rights 3.595
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.404
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 3.927
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.199
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.548
And I start Tails from USB drive "old" with network unplugged and I login 1:39.496
Then Tails is running from USB drive "old" 0.956
And I create a persistent partition 34.601
And I take note of which tps features are available 2.780
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 9.014
After features/support/hooks.rb:330 0.194
After features/support/hooks.rb:100 0.014
Tags: @product
3:23.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.289
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:38.336
Then Tails is running from USB drive "old" 0.559
And all tps features are active 4.882
When I write some files expected to persist 2.055
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.903
And I take note of which tps features are available 0.632
And I shutdown Tails and wait for the computer to power off 7.401
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.547
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.011
Tags: @product
3:11.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 30.841
And I log in to a new session 21.763
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.418
And I plug USB drive "to_upgrade" 2.477
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.898
Then the running Tails is installed on USB drive "to_upgrade" 31.263
And I unplug USB drive "to_upgrade" 0.309
And I unplug USB drive "__internal" 0.419
After features/support/hooks.rb:330 0.822
After features/support/hooks.rb:100 0.000
Tags: @product
2:46.567
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.531
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.168
Then all tps features from the old Tails version are active 2.191
And Tails is running from USB drive "to_upgrade" 0.418
And the boot device has safe access rights 3.962
And the expected persistent files created with the old Tails version are present in the filesystem 1.617
And all persistent directories from the old Tails version have safe access rights 2.676
After features/support/hooks.rb:330 1.615
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:32.229
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.891
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.202
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.359
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.610
When the network is plugged 0.085
And Tor is ready 24.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.535
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.362
Given I shutdown Tails and wait for the computer to power off 11.650
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.599
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.535
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.354
When the network is plugged 0.087
And Tor is ready 18.659
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.209
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.931
Given I shutdown Tails and wait for the computer to power off 4.525
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.377
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.639
And the file system changes introduced in version 6.3~testoverlayfs are present 0.623
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.142
And Tor is ready 19.370
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 16.307
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.873
After features/support/hooks.rb:330 0.827
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
39.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.305
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.068
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 20.195
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.620
After features/support/hooks.rb:330 0.790
After features/support/hooks.rb:100 0.000