Project Number Date
test_Tails_ISO_stable 5418 26 Jan 2025, 12:24

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 18:49.203 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:2.603
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.985
When I start Tails from USB drive "old" with network unplugged 1:28.277
Then the boot device has safe access rights 3.058
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.535
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.533
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:22.505
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 31.798
And I take note of which tps features are available 1.527
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.348
After features/support/hooks.rb:326 0.197
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.249
Before features/support/hooks.rb:269 0.006
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.485
Then Tails is running from USB drive "old" 1.732
And all tps features are active 2.253
When I write some files expected to persist 2.303
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.379
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 4.215
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.556
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.555
Before features/support/hooks.rb:269 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.193
And I log in to a new session 21.173
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.467
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.558
Then the running Tails is installed on USB drive "to_upgrade" 24.264
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:326 2.080
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.769
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.527
Then all tps features from the old Tails version are active 1.506
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 3.325
And the expected persistent files created with the old Tails version are present in the filesystem 1.456
And all persistent directories from the old Tails version have safe access rights 2.474
After features/support/hooks.rb:326 1.182
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:20.645
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.876
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.077
And Tor is ready 22.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.169
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.787
Given I shutdown Tails and wait for the computer to power off 8.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.604
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.260
And the file system changes introduced in version 6.2~testoverlayfs are present 0.389
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.304
When the network is plugged 0.064
And Tor is ready 19.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.562
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.870
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.006
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.004
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.102
And Tor is ready 19.018
Then the Upgrader considers the system as up-to-date 0.320
# 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.728
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
33.844
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.582
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.055
And the signing key used by the Upgrader is outdated 0.119
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 17.252
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.499
After features/support/hooks.rb:326 0.725
After features/support/hooks.rb:100 0.000