Project Number Date
test_Tails_ISO_stable 4790 16 Apr 2024, 20:06

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 17:26.047 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
1:40.258
Before features/support/hooks.rb:259 0.006
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 21.413
When I start Tails from USB drive "old" with network unplugged 1:13.622
Then the boot device has safe access rights 2.923
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:305 3.529
After features/support/hooks.rb:89 0.010
Tags: @product
2:0.461
Before features/support/hooks.rb:259 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:13.213
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 37.246
And I take note of which tps features are available 1.940
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 6.776
After features/support/hooks.rb:305 0.173
After features/support/hooks.rb:89 0.011
Tags: @product
2:34.732
Before features/support/hooks.rb:259 0.009
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.006
Then Tails is running from USB drive "old" 0.351
And all tps features are active 2.106
When I write some files expected to persist 1.714
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.463
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.607
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.109
After features/support/hooks.rb:305 0.133
After features/support/hooks.rb:89 0.010
Tags: @product
2:23.069
Before features/support/hooks.rb:259 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 11.848
And I log in to a new session 16.344
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.317
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.687
Then the running Tails is installed on USB drive "to_upgrade" 16.057
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:305 3.551
After features/support/hooks.rb:89 0.000
Tags: @product
2:3.750
Before features/support/hooks.rb:259 0.007
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.574
Then all tps features from the old Tails version are active 1.510
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.167
And the expected persistent files created with the old Tails version are present in the filesystem 1.482
And all persistent directories from the old Tails version have safe access rights 2.449
After features/support/hooks.rb:305 0.897
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:10.102
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.676
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.041
And Tor is ready 20.039
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.983
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.829
Given I shutdown Tails and wait for the computer to power off 6.600
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.225
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.369
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.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.299
When the network is plugged 0.035
And Tor is ready 17.277
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.990
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.960
Given I shutdown Tails and wait for the computer to power off 4.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.533
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.935
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.062
And Tor is ready 18.149
Then the Upgrader considers the system as up-to-date 0.250
# 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.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.978
After features/support/hooks.rb:305 0.804
After features/support/hooks.rb:89 0.020
Tags: @product @automatic_upgrade
33.673
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.680
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.062
And the signing key used by the Upgrader is outdated 0.613
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 17.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.281
After features/support/hooks.rb:305 0.657
After features/support/hooks.rb:89 0.000