Project Number Date
test_Tails_ISO_stable 5592 23 Apr 2025, 23:29

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 22:12.716 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:24.943
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.819
And I create a 7200 MiB disk named "old" 0.322
And I plug USB drive "old" 1.109
And I write an old version of the Tails USB image to disk "old" 32.436
When I start Tails from USB drive "old" with network unplugged 1:45.763
Then the boot device has safe access rights 3.380
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:330 9.670
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.778
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:29.256
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 33.213
And I take note of which tps features are available 2.144
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.758
After features/support/hooks.rb:330 0.209
After features/support/hooks.rb:100 0.007
Tags: @product
3:2.263
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.190
Then Tails is running from USB drive "old" 0.432
And all tps features are active 2.174
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.645
And I take note of which tps features are available 0.524
And I shutdown Tails and wait for the computer to power off 6.534
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.213
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.974
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 without a persistent partition and stopped at Tails Greeter's login screen 10.808
And I log in to a new session 21.413
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.847
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.521
Then the running Tails is installed on USB drive "to_upgrade" 29.365
And I unplug USB drive "to_upgrade" 0.282
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:330 2.724
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.248
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.287
Then all tps features from the old Tails version are active 2.041
And Tails is running from USB drive "to_upgrade" 0.433
And the boot device has safe access rights 3.688
And the expected persistent files created with the old Tails version are present in the filesystem 1.635
And all persistent directories from the old Tails version have safe access rights 2.932
After features/support/hooks.rb:330 0.824
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:33.677
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 13.406
And no SquashFS delta is installed 0.816
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.531
When the network is plugged 0.072
And Tor is ready 25.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.604
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.852
Given I shutdown Tails and wait for the computer to power off 1:40.589
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.438
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.614
And the file system changes introduced in version 6.2~testoverlayfs are present 0.394
And only the 6.2~testoverlayfs SquashFS delta is installed 0.154
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.505
# 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.405
When the network is plugged 0.103
And Tor is ready 20.028
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.345
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.355
Given I shutdown Tails and wait for the computer to power off 4.483
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.120
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.543
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.733
When the network is plugged 0.104
And Tor is ready 21.959
Then the Upgrader considers the system as up-to-date 0.314
# 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.364
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.019
After features/support/hooks.rb:330 0.846
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
44.830
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 13.527
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.988
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.588
But a current signing key is available on our website 0.000
When the network is plugged 0.273
And Tor is ready 21.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.994
After features/support/hooks.rb:330 0.858
After features/support/hooks.rb:100 0.000