Project Number Date
test_Tails_ISO_stable 5368 06 Jan 2025, 12: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 18:52.115 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:15.185
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.781
When I start Tails from USB drive "old" with network unplugged 1:38.157
Then the boot device has safe access rights 2.966
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:326 7.158
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.452
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:26.629
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 31.727
And I take note of which tps features are available 1.542
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.213
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.754
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.608
Then Tails is running from USB drive "old" 0.996
And all tps features are active 2.287
When I write some files expected to persist 2.874
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.315
And I take note of which tps features are available 0.442
And I shutdown Tails and wait for the computer to power off 4.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.063
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.011
Tags: @product
2:26.583
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.080
And I log in to a new session 19.438
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.867
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.808
Then the running Tails is installed on USB drive "to_upgrade" 19.595
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 7.058
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.505
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.151
Then all tps features from the old Tails version are active 1.612
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.145
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 2.662
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:15.453
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.176
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 0.074
And Tor is ready 20.571
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.597
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.276
Given I shutdown Tails and wait for the computer to power off 8.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.091
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.062
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.266
When the network is plugged 0.080
And Tor is ready 17.988
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.297
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.804
Given I shutdown Tails and wait for the computer to power off 4.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.826
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.886
And the file system changes introduced in version 6.3~testoverlayfs are present 0.600
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.434
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.072
And Tor is ready 16.898
Then the Upgrader considers the system as up-to-date 0.301
# 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.155
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:326 0.848
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.181
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.242
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.685
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 17.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.528
After features/support/hooks.rb:326 1.135
After features/support/hooks.rb:100 0.000