Project Number Date
test_Tails_ISO_test-suite-options 19 05 Jul 2025, 21: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 26:38.695 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:41.923
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.349
And I create a 7200 MiB disk named "old" 0.100
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 41.773
When I start Tails from USB drive "old" with network unplugged 1:48.479
Then the boot device has safe access rights 8.371
And Tails is running from USB drive "old" 0.572
And there is no persistence partition on USB drive "old" 0.203
And process "udev-watchdog" is running 0.129
And udev-watchdog is monitoring the correct device 0.597
And I unplug USB drive "old" 0.284
After features/support/hooks.rb:330 3.798
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.389
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:54.041
Then Tails is running from USB drive "old" 1.238
And I create a persistent partition 42.913
And I take note of which tps features are available 2.242
Then a Tails persistence partition exists on USB drive "old" 1.071
And I shutdown Tails and wait for the computer to power off 11.682
After features/support/hooks.rb:330 0.229
After features/support/hooks.rb:100 0.007
Tags: @product
4:3.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.388
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:6.085
Then Tails is running from USB drive "old" 0.878
And all tps features are active 2.850
When I write some files expected to persist 5.201
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.912
And all persistence configuration files have safe access rights 1.270
And all persistent directories from the old Tails version have safe access rights 4.595
And I take note of which tps features are available 0.599
And I shutdown Tails and wait for the computer to power off 4.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 36.732
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.008
Tags: @product
3:18.737
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 12.940
And I log in to a new session 28.388
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.616
And I plug USB drive "to_upgrade" 3.057
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.546
Then the running Tails is installed on USB drive "to_upgrade" 41.351
And I unplug USB drive "to_upgrade" 0.299
And I unplug USB drive "__internal" 0.537
After features/support/hooks.rb:330 3.571
After features/support/hooks.rb:100 0.000
Tags: @product
3:12.170
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:55.383
Then all tps features from the old Tails version are active 2.252
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.887
And the expected persistent files created with the old Tails version are present in the filesystem 2.368
And all persistent directories from the old Tails version have safe access rights 7.711
After features/support/hooks.rb:330 3.466
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
9:41.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.754
And no SquashFS delta is installed 0.358
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.962
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.229
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.577
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.727
When the network is plugged 0.115
And Tor is ready 30.090
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.519
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.920
Given I shutdown Tails and wait for the computer to power off 12.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:4.087
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.900
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.391
When the network is plugged 0.067
And Tor is ready 29.915
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.870
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.432
Given I shutdown Tails and wait for the computer to power off 9.109
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:58.301
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.809
And the file system changes introduced in version 6.3~testoverlayfs are present 0.760
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.072
And Tor is ready 26.092
Then the Upgrader considers the system as up-to-date 0.623
# 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 23.360
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.007
After features/support/hooks.rb:330 0.690
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
47.380
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 14.461
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.823
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.322
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.115
And Tor is ready 22.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.201
After features/support/hooks.rb:330 4.502
After features/support/hooks.rb:100 0.000