Project Number Date
test_Tails_ISO_devel 3739 14 Mar 2025, 13:39

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:2.700 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:7.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.365
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 30.468
When I start Tails from USB drive "old" with network unplugged 1:30.751
Then the boot device has safe access rights 3.347
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:330 6.986
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.006
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:26.572
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 34.530
And I take note of which tps features are available 1.994
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 8.464
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.151
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.312
Then Tails is running from USB drive "old" 0.462
And all tps features are active 2.210
When I write some files expected to persist 1.917
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 3.192
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.456
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.219
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.572
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.084
And I log in to a new session 20.872
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.691
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.949
Then the running Tails is installed on USB drive "to_upgrade" 19.089
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 2.184
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.718
Then all tps features from the old Tails version are active 1.766
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.102
And the expected persistent files created with the old Tails version are present in the filesystem 1.728
And all persistent directories from the old Tails version have safe access rights 2.659
After features/support/hooks.rb:330 0.966
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
8:11.687
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 10.845
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.581
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.103
And Tor is ready 21.897
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.120
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.971
Given I shutdown Tails and wait for the computer to power off 1:14.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.518
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 6.370
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.286
When the network is plugged 0.085
And Tor is ready 45.745
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.587
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.110
Given I shutdown Tails and wait for the computer to power off 4.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.934
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.079
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.063
And Tor is ready 17.152
Then the Upgrader considers the system as up-to-date 10.920
# 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 14.727
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.048
After features/support/hooks.rb:330 0.803
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.597
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 10.925
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.123
But a current signing key is available on our website 0.000
When the network is plugged 0.120
And Tor is ready 20.094
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.883
After features/support/hooks.rb:330 1.219
After features/support/hooks.rb:100 0.000