Project Number Date
test_Tails_ISO_stable 5370 07 Jan 2025, 09:20

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 19:39.083 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:19.057
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.965
When I start Tails from USB drive "old" with network unplugged 1:40.494
Then the boot device has safe access rights 3.307
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.531
After features/support/hooks.rb:100 0.065
Tags: @product
2:10.152
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:25.340
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 33.703
And I take note of which tps features are available 1.388
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.347
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.930
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.685
Then Tails is running from USB drive "old" 2.080
And all tps features are active 1.982
When I write some files expected to persist 1.815
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.286
And all persistence configuration files have safe access rights 0.497
And all persistent directories from the old Tails version have safe access rights 2.514
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.181
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.748
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 9.240
And I log in to a new session 18.751
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.665
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.770
Then the running Tails is installed on USB drive "to_upgrade" 22.471
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 6.758
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.275
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.702
Then all tps features from the old Tails version are active 1.929
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.732
And the expected persistent files created with the old Tails version are present in the filesystem 1.562
And all persistent directories from the old Tails version have safe access rights 2.748
After features/support/hooks.rb:326 0.605
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:31.572
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 14.012
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.374
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.074
And Tor is ready 21.268
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.620
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.051
Given I shutdown Tails and wait for the computer to power off 10.936
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.001
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.273
When the network is plugged 0.062
And Tor is ready 19.269
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.095
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.815
Given I shutdown Tails and wait for the computer to power off 4.346
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.771
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.390
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.078
And Tor is ready 18.298
Then the Upgrader considers the system as up-to-date 0.325
# 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.405
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.058
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
58.346
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.457
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.756
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 46.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.624
After features/support/hooks.rb:326 0.860
After features/support/hooks.rb:100 0.000