Project Number Date
test_Tails_ISO_fix-homepage-image 5 15 Jul 2025, 08:07

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 20:12.867 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:1.094
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 28.326
When I start Tails from USB drive "old" with network unplugged 1:27.424
Then the boot device has safe access rights 3.048
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:330 4.138
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:28.090
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 29.787
And I take note of which tps features are available 2.486
Then a Tails persistence partition exists on USB drive "old" 0.773
And I shutdown Tails and wait for the computer to power off 6.909
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.447
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.800
Then Tails is running from USB drive "old" 0.360
And all tps features are active 2.572
When I write some files expected to persist 2.412
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.501
And all persistent directories from the old Tails version have safe access rights 2.905
And I take note of which tps features are available 0.568
And I shutdown Tails and wait for the computer to power off 4.350
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.505
After features/support/hooks.rb:330 0.355
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.786
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.499
And I log in to a new session 20.080
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.626
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.082
Then the running Tails is installed on USB drive "to_upgrade" 24.685
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 0.927
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.946
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.282
And the expected persistent files created with the old Tails version are present in the filesystem 1.478
And all persistent directories from the old Tails version have safe access rights 2.687
After features/support/hooks.rb:330 1.411
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:59.233
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 13.261
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.564
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.116
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.372
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.558
When the network is plugged 0.135
And Tor is ready 23.399
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.491
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.272
Given I shutdown Tails and wait for the computer to power off 11.201
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.575
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.523
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.551
When the network is plugged 0.071
And Tor is ready 22.068
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.324
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.431
Given I shutdown Tails and wait for the computer to power off 6.921
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.707
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.366
And the file system changes introduced in version 6.3~testoverlayfs are present 0.546
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.442
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.112
And Tor is ready 18.706
Then the Upgrader considers the system as up-to-date 0.439
# 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 17.234
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.444
After features/support/hooks.rb:330 0.825
After features/support/hooks.rb:100 0.102
Tags: @product @automatic_upgrade
59.018
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 with a persistent partition enabled and logged in 10.662
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.541
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 46.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.599
After features/support/hooks.rb:330 0.940
After features/support/hooks.rb:100 0.000