Project Number Date
test_Tails_ISO_feature-arti 102 30 Jun 2025, 18:10

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 21:7.802 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:25.075
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.777
When I start Tails from USB drive "old" with network unplugged 1:50.146
Then the boot device has safe access rights 3.836
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 3.539
After features/support/hooks.rb:100 0.016
Tags: @product
2:22.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 1:37.058
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 32.982
And I take note of which tps features are available 2.607
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 8.855
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.020
Tags: @product
3:2.754
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.653
Then Tails is running from USB drive "old" 0.421
And all tps features are active 2.203
When I write some files expected to persist 2.724
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.323
And all persistence configuration files have safe access rights 0.630
And all persistent directories from the old Tails version have safe access rights 3.663
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 4.525
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.877
After features/support/hooks.rb:330 0.095
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.291
And I log in to a new session 21.769
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.385
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.482
Then the running Tails is installed on USB drive "to_upgrade" 31.330
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.409
After features/support/hooks.rb:330 1.049
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.408
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.454
Then all tps features from the old Tails version are active 2.050
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.767
And the expected persistent files created with the old Tails version are present in the filesystem 1.332
And all persistent directories from the old Tails version have safe access rights 2.238
After features/support/hooks.rb:330 1.462
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:17.887
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 12.091
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.505
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.381
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.071
And Tor is ready 22.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.488
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.022
Given I shutdown Tails and wait for the computer to power off 9.685
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.649
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.548
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.177
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.641
# 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.606
When the network is plugged 0.078
And Tor is ready 19.133
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.060
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.629
Given I shutdown Tails and wait for the computer to power off 6.597
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.470
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.195
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.068
And Tor is ready 21.391
Then the Upgrader considers the system as up-to-date 0.283
# 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 17.557
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.515
After features/support/hooks.rb:330 0.722
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
44.572
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 with a persistent partition enabled and logged in 11.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 24.061
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.604
After features/support/hooks.rb:330 0.859
After features/support/hooks.rb:100 0.000