Project Number Date
test_Tails_ISO_devel 3735 12 Mar 2025, 15:09

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:9.578 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:0.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.907
When I start Tails from USB drive "old" with network unplugged 1:24.151
Then the boot device has safe access rights 3.394
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.355
After features/support/hooks.rb:330 3.873
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:26.444
Then Tails is running from USB drive "old" 0.467
And I create a persistent partition 31.207
And I take note of which tps features are available 3.231
Then a Tails persistence partition exists on USB drive "old" 0.856
And I shutdown Tails and wait for the computer to power off 8.325
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.486
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.088
Then Tails is running from USB drive "old" 1.018
And all tps features are active 1.909
When I write some files expected to persist 1.828
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 3.110
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.373
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.867
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.066
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.962
And I log in to a new session 19.937
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.731
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.006
Then the running Tails is installed on USB drive "to_upgrade" 19.575
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 2.607
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.940
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.627
Then all tps features from the old Tails version are active 1.612
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.444
And the expected persistent files created with the old Tails version are present in the filesystem 1.420
And all persistent directories from the old Tails version have safe access rights 2.334
After features/support/hooks.rb:330 0.998
After features/support/hooks.rb:100 0.007
6:44.204
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.011
And no SquashFS delta is installed 0.252
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.083
And Tor is ready 20.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.066
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.352
Given I shutdown Tails and wait for the computer to power off 8.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.215
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 1.950
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.283
When the network is plugged 0.065
And Tor is ready 18.930
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.545
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.789
Given I shutdown Tails and wait for the computer to power off 4.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.436
Then Tails is running version 6.3~testoverlayfs 0.037
And all tps features are active 2.047
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.383
When the network is plugged 0.075
And Tor is ready 18.179
Then the Upgrader considers the system as up-to-date 0.326
# 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.487
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.173
After features/support/hooks.rb:330 0.799
After features/support/hooks.rb:100 0.018
38.222
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.622
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 22.002
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.983
After features/support/hooks.rb:330 1.380
After features/support/hooks.rb:100 0.000