Project Number Date
test_Tails_ISO_stable 4959 21 Jul 2024, 12:16

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:51.181 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:5.142
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.958
When I start Tails from USB drive "old" with network unplugged 1:30.986
Then the boot device has safe access rights 2.936
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 7.235
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.087
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:21.408
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 31.006
And I take note of which tps features are available 1.920
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.393
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.725
Before features/support/hooks.rb:269 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.594
Then Tails is running from USB drive "old" 0.336
And all tps features are active 2.032
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 2.344
And I take note of which tps features are available 0.566
And I shutdown Tails and wait for the computer to power off 4.175
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.170
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.508
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.449
And I log in to a new session 23.331
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.392
And I plug USB drive "to_upgrade" 2.369
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.220
Then the running Tails is installed on USB drive "to_upgrade" 19.269
And I unplug USB drive "to_upgrade" 0.270
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.301
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.011
Before features/support/hooks.rb:269 0.006
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.616
Then all tps features from the old Tails version are active 1.655
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.349
And the expected persistent files created with the old Tails version are present in the filesystem 1.438
And all persistent directories from the old Tails version have safe access rights 2.410
After features/support/hooks.rb:326 0.664
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:4.431
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.686
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.050
And Tor is ready 21.916
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.349
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.183
Given I shutdown Tails and wait for the computer to power off 8.672
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.401
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.032
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.274
When the network is plugged 0.038
And Tor is ready 16.908
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.585
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.550
Given I shutdown Tails and wait for the computer to power off 57.188
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.010
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.223
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.043
And Tor is ready 18.080
Then the Upgrader considers the system as up-to-date 0.321
# 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.737
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
57.275
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.872
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 44.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.577
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.000