Project Number Date
test_Tails_ISO_stable 5258 09 Nov 2024, 12:44

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 20:24.339 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:18.614
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.878
When I start Tails from USB drive "old" with network unplugged 1:40.212
Then the boot device has safe access rights 3.172
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 3.769
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.720
Before features/support/hooks.rb:269 0.006
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:27.639
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 31.499
And I take note of which tps features are available 2.047
Then a Tails persistence partition exists on USB drive "old" 0.959
And I shutdown Tails and wait for the computer to power off 6.985
After features/support/hooks.rb:326 0.194
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.832
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.110
Then Tails is running from USB drive "old" 0.558
And all tps features are active 2.003
When I write some files expected to persist 1.745
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.876
And I take note of which tps features are available 0.598
And I shutdown Tails and wait for the computer to power off 4.198
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.891
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.223
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.587
And I log in to a new session 21.506
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.819
And I plug USB drive "to_upgrade" 2.496
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.043
Then the running Tails is installed on USB drive "to_upgrade" 21.652
And I unplug USB drive "to_upgrade" 0.846
And I unplug USB drive "__internal" 0.269
After features/support/hooks.rb:326 1.966
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.092
Before features/support/hooks.rb:269 0.008
Given a computer 0.254
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.905
Then all tps features from the old Tails version are active 2.086
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.930
And the expected persistent files created with the old Tails version are present in the filesystem 1.804
And all persistent directories from the old Tails version have safe access rights 2.734
After features/support/hooks.rb:326 0.793
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:6.402
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 13.014
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.153
And Tor is ready 51.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.444
Given I shutdown Tails and wait for the computer to power off 9.109
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.037
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.586
And the file system changes introduced in version 6.2~testoverlayfs are present 0.359
And only the 6.2~testoverlayfs SquashFS delta is installed 0.104
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.388
# 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.339
When the network is plugged 0.096
And Tor is ready 21.948
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.594
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.612
Given I shutdown Tails and wait for the computer to power off 4.394
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.557
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.588
And the file system changes introduced in version 6.3~testoverlayfs are present 1.154
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.412
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.470
When the network is plugged 0.096
And Tor is ready 18.700
Then the Upgrader considers the system as up-to-date 0.341
# 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.892
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.185
After features/support/hooks.rb:326 0.754
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
43.453
Before features/support/hooks.rb:269 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.299
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.175
And the signing key used by the Upgrader is outdated 1.363
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 21.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.033
After features/support/hooks.rb:326 0.900
After features/support/hooks.rb:100 0.000