Project Number Date
test_Tails_ISO_devel 3722 04 Mar 2025, 23:27

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:16.590 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:8.207
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.081
When I start Tails from USB drive "old" with network unplugged 1:32.702
Then the boot device has safe access rights 3.096
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:330 11.405
After features/support/hooks.rb:100 0.018
Tags: @product
2:1.612
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login 1:20.913
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 31.649
And I take note of which tps features are available 1.304
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 6.327
After features/support/hooks.rb:330 0.239
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.221
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.718
Then Tails is running from USB drive "old" 0.804
And all tps features are active 1.865
When I write some files expected to persist 1.640
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 3.165
And I take note of which tps features are available 0.582
And I shutdown Tails and wait for the computer to power off 4.698
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.906
After features/support/hooks.rb:330 0.099
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.494
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 10.612
And I log in to a new session 18.574
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.917
And I plug USB drive "to_upgrade" 2.384
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.739
Then the running Tails is installed on USB drive "to_upgrade" 21.866
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 2.461
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.328
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.947
Then all tps features from the old Tails version are active 1.603
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.040
And the expected persistent files created with the old Tails version are present in the filesystem 1.812
And all persistent directories from the old Tails version have safe access rights 2.404
After features/support/hooks.rb:330 1.945
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:46.300
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.130
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
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.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.065
And Tor is ready 48.053
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.569
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.730
Given I shutdown Tails and wait for the computer to power off 8.627
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.887
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.975
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.252
When the network is plugged 0.076
And Tor is ready 18.315
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.537
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.808
Given I shutdown Tails and wait for the computer to power off 4.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.216
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.059
And Tor is ready 19.758
Then the Upgrader considers the system as up-to-date 0.285
# 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.551
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.878
After features/support/hooks.rb:330 0.766
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
33.426
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 9.776
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.100
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 16.717
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.244
After features/support/hooks.rb:330 1.127
After features/support/hooks.rb:100 0.000