Project Number Date
test_Tails_ISO_devel 3661 25 Jan 2025, 17:36

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:10.465 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:13.413
Before features/support/hooks.rb:269 0.003
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.561
When I start Tails from USB drive "old" with network unplugged 1:38.306
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.577
After features/support/hooks.rb:100 0.031
Tags: @product
2:15.270
Before features/support/hooks.rb:269 0.003
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:32.704
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 31.491
And I take note of which tps features are available 1.413
Then a Tails persistence partition exists on USB drive "old" 0.837
And I shutdown Tails and wait for the computer to power off 8.270
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.006
Tags: @product
2:56.866
Before features/support/hooks.rb:269 0.003
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.150
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.092
When I write some files expected to persist 2.069
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.415
And I take note of which tps features are available 0.564
And I shutdown Tails and wait for the computer to power off 4.778
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.667
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.006
Tags: @product
2:32.608
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.414
And I log in to a new session 20.775
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.706
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.727
Then the running Tails is installed on USB drive "to_upgrade" 23.168
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.348
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.490
Before features/support/hooks.rb:269 0.002
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.515
Then all tps features from the old Tails version are active 1.757
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.743
And the expected persistent files created with the old Tails version are present in the filesystem 1.475
And all persistent directories from the old Tails version have safe access rights 2.504
After features/support/hooks.rb:326 1.002
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
6:10.536
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.317
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.068
And Tor is ready 17.328
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.533
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.482
Given I shutdown Tails and wait for the computer to power off 8.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.252
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.281
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.264
When the network is plugged 0.085
And Tor is ready 19.308
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.946
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.011
Given I shutdown Tails and wait for the computer to power off 4.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.046
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.064
And Tor is ready 20.192
Then the Upgrader considers the system as up-to-date 0.328
# 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.677
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.995
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
33.279
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.036
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 16.244
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.437
After features/support/hooks.rb:326 0.647
After features/support/hooks.rb:100 0.000