Project Number Date
test_Tails_ISO_stable 5304 29 Nov 2024, 12:50

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:45.863 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:23.198
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.647
When I start Tails from USB drive "old" with network unplugged 1:44.989
Then the boot device has safe access rights 3.228
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.748
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.681
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:29.066
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 31.518
And I take note of which tps features are available 1.806
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 8.838
After features/support/hooks.rb:326 0.217
After features/support/hooks.rb:100 0.010
Tags: @product
3:13.936
Before features/support/hooks.rb:269 0.004
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.520
Then Tails is running from USB drive "old" 0.453
And all tps features are active 2.486
When I write some files expected to persist 2.181
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.282
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.705
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 4.402
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.802
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.690
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 13.476
And I log in to a new session 19.804
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.725
And I plug USB drive "to_upgrade" 2.578
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.063
Then the running Tails is installed on USB drive "to_upgrade" 23.573
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 3.651
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.771
Before features/support/hooks.rb:269 0.008
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.468
Then all tps features from the old Tails version are active 1.757
And Tails is running from USB drive "to_upgrade" 0.512
And the boot device has safe access rights 4.090
And the expected persistent files created with the old Tails version are present in the filesystem 1.626
And all persistent directories from the old Tails version have safe access rights 3.078
After features/support/hooks.rb:326 0.880
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:14.545
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 16.619
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.569
When the network is plugged 0.079
And Tor is ready 23.961
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.956
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.704
Given I shutdown Tails and wait for the computer to power off 11.216
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.993
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.247
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.325
When the network is plugged 0.073
And Tor is ready 47.935
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.678
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.410
Given I shutdown Tails and wait for the computer to power off 4.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.058
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.032
And the file system changes introduced in version 6.3~testoverlayfs are present 0.587
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.103
And Tor is ready 19.799
Then the Upgrader considers the system as up-to-date 0.426
# 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 15.784
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.115
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
41.037
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.882
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 21.619
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.698
After features/support/hooks.rb:326 1.089
After features/support/hooks.rb:100 0.000