Project Number Date
test_Tails_ISO_stable 5010 08 Aug 2024, 12:40

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:20.534 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:41.733
Before features/support/hooks.rb:269 0.009
Given a computer 0.309
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 45.371
When I start Tails from USB drive "old" with network unplugged 1:50.563
Then the boot device has safe access rights 3.321
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:326 3.546
After features/support/hooks.rb:100 0.015
Tags: @product
2:22.107
Before features/support/hooks.rb:269 0.009
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:33.265
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 36.159
And I take note of which tps features are available 2.117
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 9.109
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.015
Tags: @product
3:14.853
Before features/support/hooks.rb:269 0.009
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.846
Then Tails is running from USB drive "old" 0.591
And all tps features are active 2.396
When I write some files expected to persist 1.898
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.825
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.713
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.186
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.155
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.273
And I log in to a new session 28.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.868
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.894
Then the running Tails is installed on USB drive "to_upgrade" 17.352
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.068
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.065
Before features/support/hooks.rb:269 0.009
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.716
Then all tps features from the old Tails version are active 1.807
And Tails is running from USB drive "to_upgrade" 0.406
And the boot device has safe access rights 3.518
And the expected persistent files created with the old Tails version are present in the filesystem 1.500
And all persistent directories from the old Tails version have safe access rights 2.914
After features/support/hooks.rb:326 0.688
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
8:15.210
Before features/support/hooks.rb:269 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.789
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.073
And Tor is ready 21.772
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.941
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.353
Given I shutdown Tails and wait for the computer to power off 1:23.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.997
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.473
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.304
When the network is plugged 0.074
And Tor is ready 19.419
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.831
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.252
Given I shutdown Tails and wait for the computer to power off 4.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.992
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.167
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.070
And Tor is ready 20.033
Then the Upgrader considers the system as up-to-date 0.342
# 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 13.959
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.066
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
36.408
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.387
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.872
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 19.554
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.092
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.000