Project Number Date
test_Tails_ISO_devel 3710 26 Feb 2025, 12:43

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:9.384 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
1:59.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.251
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.761
When I start Tails from USB drive "old" with network unplugged 1:23.859
Then the boot device has safe access rights 3.044
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 3.510
After features/support/hooks.rb:100 0.032
Tags: @product
2:7.570
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:21.142
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 32.533
And I take note of which tps features are available 1.506
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 11.042
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.905
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.263
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.446
Then Tails is running from USB drive "old" 0.607
And all tps features are active 2.010
When I write some files expected to persist 1.826
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.547
And all persistent directories from the old Tails version have safe access rights 3.355
And I take note of which tps features are available 0.637
And I shutdown Tails and wait for the computer to power off 6.515
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.465
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.455
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 13.339
And I log in to a new session 20.445
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.030
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.969
Then the running Tails is installed on USB drive "to_upgrade" 22.767
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 3.135
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.269
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.618
Then all tps features from the old Tails version are active 1.697
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.236
And the expected persistent files created with the old Tails version are present in the filesystem 1.689
And all persistent directories from the old Tails version have safe access rights 2.546
After features/support/hooks.rb:330 1.128
After features/support/hooks.rb:100 0.011
6:33.168
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 14.175
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.448
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.585
When the network is plugged 0.069
And Tor is ready 29.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.056
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.453
Given I shutdown Tails and wait for the computer to power off 12.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.640
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.280
# 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.272
When the network is plugged 0.096
And Tor is ready 19.606
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.591
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.436
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.408
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.969
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.371
When the network is plugged 0.074
And Tor is ready 16.892
Then the Upgrader considers the system as up-to-date 0.373
# 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.794
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.264
After features/support/hooks.rb:330 0.782
After features/support/hooks.rb:100 0.015
41.984
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 11.702
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.047
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 22.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.822
After features/support/hooks.rb:330 3.308
After features/support/hooks.rb:100 0.000