Project Number Date
test_Tails_ISO_devel 3776 10 Apr 2025, 15:28

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 22:24.093 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:43.340
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.302
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 57.247
When I start Tails from USB drive "old" with network unplugged 1:39.999
Then the boot device has safe access rights 3.581
And Tails is running from USB drive "old" 0.402
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 12.738
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login 1:40.268
Then Tails is running from USB drive "old" 0.546
And I create a persistent partition 34.556
And I take note of which tps features are available 2.781
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 9.001
After features/support/hooks.rb:330 0.186
After features/support/hooks.rb:100 0.010
Tags: @product
3:26.611
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:38.173
Then Tails is running from USB drive "old" 1.008
And all tps features are active 3.933
When I write some files expected to persist 3.149
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 3.095
And I take note of which tps features are available 0.839
And I shutdown Tails and wait for the computer to power off 6.272
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.169
After features/support/hooks.rb:330 0.202
After features/support/hooks.rb:100 0.020
Tags: @product
3:6.210
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 38.370
And I log in to a new session 20.268
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.949
And I plug USB drive "to_upgrade" 2.527
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.471
Then the running Tails is installed on USB drive "to_upgrade" 22.110
And I unplug USB drive "to_upgrade" 0.272
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:330 6.897
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.587
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.551
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.913
Then all tps features from the old Tails version are active 2.328
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.864
And the expected persistent files created with the old Tails version are present in the filesystem 2.405
And all persistent directories from the old Tails version have safe access rights 3.117
After features/support/hooks.rb:330 1.342
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:25.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.209
And no SquashFS delta is installed 0.231
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.773
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.485
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.710
When the network is plugged 0.117
And Tor is ready 25.693
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.678
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.382
Given I shutdown Tails and wait for the computer to power off 11.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.255
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 3.504
And the file system changes introduced in version 6.2~testoverlayfs are present 0.399
And only the 6.2~testoverlayfs SquashFS delta is installed 0.115
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.387
# 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.366
When the network is plugged 0.126
And Tor is ready 21.313
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.636
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.781
Given I shutdown Tails and wait for the computer to power off 6.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.793
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.914
And the file system changes introduced in version 6.3~testoverlayfs are present 0.629
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.386
When the network is plugged 0.155
And Tor is ready 20.771
Then the Upgrader considers the system as up-to-date 0.345
# 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.850
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.130
After features/support/hooks.rb:330 0.785
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
44.876
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.616
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.481
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.133
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 21.268
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.218
After features/support/hooks.rb:330 2.161
After features/support/hooks.rb:100 0.000