Project Number Date
test_Tails_ISO_stable 4992 01 Aug 2024, 21:48

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:19.391 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:42.762
Before features/support/hooks.rb:269 0.007
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.113
And I write an old version of the Tails USB image to disk "old" 40.408
When I start Tails from USB drive "old" with network unplugged 1:56.870
Then the boot device has safe access rights 3.063
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 7.242
After features/support/hooks.rb:100 0.022
Tags: @product
2:10.448
Before features/support/hooks.rb:269 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:27.102
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 32.357
And I take note of which tps features are available 1.387
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 8.220
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.082
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.039
Then Tails is running from USB drive "old" 0.438
And all tps features are active 2.217
When I write some files expected to persist 1.933
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.657
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.194
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.280
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.013
Tags: @product
2:34.678
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.500
And I log in to a new session 19.797
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.578
And I plug USB drive "to_upgrade" 2.447
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.541
Then the running Tails is installed on USB drive "to_upgrade" 23.390
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 1.988
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.827
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.808
Then all tps features from the old Tails version are active 1.744
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.089
And the expected persistent files created with the old Tails version are present in the filesystem 1.688
And all persistent directories from the old Tails version have safe access rights 2.914
After features/support/hooks.rb:326 1.068
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:50.337
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 11.276
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.543
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.047
And Tor is ready 21.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.466
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.862
Given I shutdown Tails and wait for the computer to power off 8.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.121
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.314
And the file system changes introduced in version 6.2~testoverlayfs are present 0.379
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# 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.295
When the network is plugged 0.038
And Tor is ready 48.285
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.590
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.962
Given I shutdown Tails and wait for the computer to power off 4.255
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.734
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.220
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.046
And Tor is ready 20.312
Then the Upgrader considers the system as up-to-date 0.338
# 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.745
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.226
After features/support/hooks.rb:326 0.839
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
37.254
Before features/support/hooks.rb:269 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.269
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.409
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 18.264
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.790
After features/support/hooks.rb:326 1.006
After features/support/hooks.rb:100 0.000