Project Number Date
test_Tails_ISO_20872-more-gtk-launch 5 30 Mar 2025, 08: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:5.313 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:3.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.737
When I start Tails from USB drive "old" with network unplugged 1:27.631
Then the boot device has safe access rights 2.934
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 7.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.429
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:22.842
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 31.032
And I take note of which tps features are available 1.851
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.803
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.507
Then Tails is running from USB drive "old" 0.360
And all tps features are active 1.940
When I write some files expected to persist 1.751
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.358
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.501
And I take note of which tps features are available 0.411
And I shutdown Tails and wait for the computer to power off 4.341
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.986
After features/support/hooks.rb:330 0.122
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.387
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.350
And I log in to a new session 22.127
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.456
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.055
Then the running Tails is installed on USB drive "to_upgrade" 20.550
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 0.949
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.263
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.561
Then all tps features from the old Tails version are active 1.746
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.025
And the expected persistent files created with the old Tails version are present in the filesystem 1.400
And all persistent directories from the old Tails version have safe access rights 3.020
After features/support/hooks.rb:330 1.583
After features/support/hooks.rb:100 0.063
Tags: @product @automatic_upgrade
6:25.233
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.935
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.068
And Tor is ready 21.589
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.495
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.297
Given I shutdown Tails and wait for the computer to power off 8.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.511
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.274
# 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.280
When the network is plugged 0.082
And Tor is ready 19.366
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.625
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.916
Given I shutdown Tails and wait for the computer to power off 4.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.176
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.490
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.093
And Tor is ready 18.621
Then the Upgrader considers the system as up-to-date 0.299
# 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.605
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.649
After features/support/hooks.rb:330 0.683
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
38.590
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 9.682
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.107
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 20.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.005
After features/support/hooks.rb:330 1.168
After features/support/hooks.rb:100 0.000