Project Number Date
test_Tails_ISO_stable 5240 31 Oct 2024, 13:10

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 23:40.102 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
3:22.935
Before features/support/hooks.rb:269 0.010
Given a computer 0.312
And I create a 7200 MiB disk named "old" 0.079
And I plug USB drive "old" 1.078
And I write an old version of the Tails USB image to disk "old" 1:24.783
When I start Tails from USB drive "old" with network unplugged 1:52.204
Then the boot device has safe access rights 3.367
And Tails is running from USB drive "old" 0.400
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.241
After features/support/hooks.rb:326 3.675
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.606
Before features/support/hooks.rb:269 0.007
Given a computer 0.891
And I start Tails from USB drive "old" with network unplugged and I login 1:37.117
Then Tails is running from USB drive "old" 0.415
And I create a persistent partition 44.454
And I take note of which tps features are available 8.789
Then a Tails persistence partition exists on USB drive "old" 1.322
And I shutdown Tails and wait for the computer to power off 8.616
After features/support/hooks.rb:326 0.195
After features/support/hooks.rb:100 0.011
Tags: @product
3:22.547
Before features/support/hooks.rb:269 0.006
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:44.100
Then Tails is running from USB drive "old" 0.560
And all tps features are active 2.489
When I write some files expected to persist 1.856
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.716
And I take note of which tps features are available 0.549
And I shutdown Tails and wait for the computer to power off 4.475
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.896
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.883
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 27.976
And I log in to a new session 19.712
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.238
And I plug USB drive "to_upgrade" 2.538
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.055
Then the running Tails is installed on USB drive "to_upgrade" 25.882
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:326 3.616
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.961
Before features/support/hooks.rb:269 0.006
Given a computer 0.322
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.103
Then all tps features from the old Tails version are active 4.639
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.364
And the expected persistent files created with the old Tails version are present in the filesystem 1.543
And all persistent directories from the old Tails version have safe access rights 2.639
After features/support/hooks.rb:326 1.010
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:54.144
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 31.476
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.554
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.100
And Tor is ready 26.992
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.065
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.550
Given I shutdown Tails and wait for the computer to power off 13.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.113
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 2.885
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.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.427
# 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.327
When the network is plugged 0.187
And Tor is ready 19.755
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.895
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.957
Given I shutdown Tails and wait for the computer to power off 7.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.066
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.711
And the file system changes introduced in version 6.3~testoverlayfs are present 0.622
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.363
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.347
When the network is plugged 0.085
And Tor is ready 48.623
Then the Upgrader considers the system as up-to-date 0.335
# 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.370
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.089
After features/support/hooks.rb:326 0.867
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
47.023
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 15.556
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.915
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 23.966
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.983
After features/support/hooks.rb:326 0.823
After features/support/hooks.rb:100 0.000