Project Number Date
test_Tails_ISO_devel 3732 11 Mar 2025, 13:06

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:15.718 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:31.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 33.215
When I start Tails from USB drive "old" with network unplugged 1:52.634
Then the boot device has safe access rights 3.537
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.371
And I unplug USB drive "old" 0.241
After features/support/hooks.rb:330 7.100
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:24.272
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 33.039
And I take note of which tps features are available 2.051
Then a Tails persistence partition exists on USB drive "old" 0.928
And I shutdown Tails and wait for the computer to power off 8.820
After features/support/hooks.rb:330 0.207
After features/support/hooks.rb:100 0.011
Tags: @product
3:8.274
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.305
Then Tails is running from USB drive "old" 0.583
And all tps features are active 2.426
When I write some files expected to persist 1.932
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.652
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 6.248
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.777
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.133
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.251
And I log in to a new session 21.162
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.499
And I plug USB drive "to_upgrade" 2.525
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.015
Then the running Tails is installed on USB drive "to_upgrade" 22.230
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:330 2.135
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.210
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
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.238
Then all tps features from the old Tails version are active 1.792
And Tails is running from USB drive "to_upgrade" 0.482
And the boot device has safe access rights 3.372
And the expected persistent files created with the old Tails version are present in the filesystem 1.546
And all persistent directories from the old Tails version have safe access rights 2.593
After features/support/hooks.rb:330 1.363
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:51.434
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.524
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.420
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.397
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.065
And Tor is ready 22.501
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.728
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.567
Given I shutdown Tails and wait for the computer to power off 8.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.825
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.621
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# 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.290
When the network is plugged 0.074
And Tor is ready 18.143
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.630
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.245
Given I shutdown Tails and wait for the computer to power off 4.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.941
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.006
And the file system changes introduced in version 6.3~testoverlayfs are present 0.590
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.152
And Tor is ready 19.972
Then the Upgrader considers the system as up-to-date 0.341
# 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.965
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.149
After features/support/hooks.rb:330 0.859
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
40.122
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.641
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.140
But a current signing key is available on our website 0.000
When the network is plugged 0.192
And Tor is ready 20.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.554
After features/support/hooks.rb:330 1.479
After features/support/hooks.rb:100 0.000