Project Number Date
test_Tails_ISO_stable 5140 03 Oct 2024, 22: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:51.991 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:12.568
Before features/support/hooks.rb:269 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 33.608
When I start Tails from USB drive "old" with network unplugged 1:33.426
Then the boot device has safe access rights 3.236
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.456
After features/support/hooks.rb:100 0.046
Tags: @product
2:7.970
Before features/support/hooks.rb:269 0.003
Given a computer 0.288
And I start Tails from USB drive "old" with network unplugged and I login 1:24.014
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 32.149
And I take note of which tps features are available 2.022
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.315
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.258
Before features/support/hooks.rb:269 0.004
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.353
Then Tails is running from USB drive "old" 0.350
And all tps features are active 2.104
When I write some files expected to persist 1.924
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.365
And all persistence configuration files have safe access rights 0.532
And all persistent directories from the old Tails version have safe access rights 2.516
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.121
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.796
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.358
And I log in to a new session 25.150
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.603
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.368
Then the running Tails is installed on USB drive "to_upgrade" 22.532
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 3.751
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.406
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.291
Then all tps features from the old Tails version are active 1.991
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.741
And the expected persistent files created with the old Tails version are present in the filesystem 1.416
And all persistent directories from the old Tails version have safe access rights 2.445
After features/support/hooks.rb:326 1.005
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:8.308
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 14.347
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.099
And Tor is ready 50.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.625
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.619
Given I shutdown Tails and wait for the computer to power off 12.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.695
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 7.015
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.390
When the network is plugged 0.620
And Tor is ready 19.211
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.934
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.356
Given I shutdown Tails and wait for the computer to power off 4.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.018
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.138
And the file system changes introduced in version 6.3~testoverlayfs are present 0.632
And only the 6.3~testoverlayfs SquashFS delta is installed 0.114
# 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.432
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.064
And Tor is ready 20.146
Then the Upgrader considers the system as up-to-date 0.327
# 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.292
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.231
After features/support/hooks.rb:326 0.787
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.683
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.293
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
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.799
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 19.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.601
After features/support/hooks.rb:326 1.379
After features/support/hooks.rb:100 0.000