Project Number Date
test_Tails_ISO_stable 4924 09 Jul 2024, 14:11

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 22:32.335 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:35.842
Before features/support/hooks.rb:269 0.006
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 33.191
When I start Tails from USB drive "old" with network unplugged 1:57.108
Then the boot device has safe access rights 3.151
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 7.207
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.446
Before features/support/hooks.rb:269 0.006
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login 1:28.952
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 31.727
And I take note of which tps features are available 1.490
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.862
After features/support/hooks.rb:326 0.233
After features/support/hooks.rb:100 0.012
Tags: @product
3:12.153
Before features/support/hooks.rb:269 0.008
Given a computer 0.328
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.750
Then Tails is running from USB drive "old" 0.460
And all tps features are active 2.480
When I write some files expected to persist 2.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.274
And all persistence configuration files have safe access rights 0.507
And all persistent directories from the old Tails version have safe access rights 2.965
And I take note of which tps features are available 0.657
And I shutdown Tails and wait for the computer to power off 4.275
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.385
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.012
Tags: @product
2:53.065
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 23.461
And I log in to a new session 20.809
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.444
And I plug USB drive "to_upgrade" 2.514
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.124
Then the running Tails is installed on USB drive "to_upgrade" 21.290
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 7.516
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.877
Before features/support/hooks.rb:269 0.008
Given a computer 0.620
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:31.330
Then all tps features from the old Tails version are active 1.823
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.600
And the expected persistent files created with the old Tails version are present in the filesystem 1.513
And all persistent directories from the old Tails version have safe access rights 2.607
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
8:21.451
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.710
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
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.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.049
And Tor is ready 24.015
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.507
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.937
Given I shutdown Tails and wait for the computer to power off 1:26.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.908
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.303
When the network is plugged 0.043
And Tor is ready 20.779
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.782
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.707
Given I shutdown Tails and wait for the computer to power off 4.713
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.487
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.443
And the file system changes introduced in version 6.3~testoverlayfs are present 0.560
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.394
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.040
And Tor is ready 18.690
Then the Upgrader considers the system as up-to-date 0.339
# 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.702
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.104
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.067
Tags: @product @automatic_upgrade
35.498
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.894
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.845
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 17.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.700
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.000