Project Number Date
test_Tails_ISO_stable 5433 30 Jan 2025, 12:50

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 21:9.837 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:13.069
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.872
When I start Tails from USB drive "old" with network unplugged 1:38.692
Then the boot device has safe access rights 3.143
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 7.274
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.547
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:24.336
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 36.591
And I take note of which tps features are available 1.791
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.467
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.007
Tags: @product
2:48.505
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.602
Then Tails is running from USB drive "old" 0.511
And all tps features are active 2.008
When I write some files expected to persist 1.806
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.561
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.421
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.254
After features/support/hooks.rb:326 0.092
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.403
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.993
And I log in to a new session 22.763
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.732
And I plug USB drive "to_upgrade" 2.353
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.491
Then the running Tails is installed on USB drive "to_upgrade" 21.160
And I unplug USB drive "to_upgrade" 0.495
And I unplug USB drive "__internal" 0.412
After features/support/hooks.rb:326 2.165
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.367
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.641
Then all tps features from the old Tails version are active 1.688
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.440
And all persistent directories from the old Tails version have safe access rights 2.573
After features/support/hooks.rb:326 0.712
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:23.049
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.580
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.443
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.068
And Tor is ready 51.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.612
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.789
Given I shutdown Tails and wait for the computer to power off 1:11.801
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.087
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.160
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.254
When the network is plugged 0.083
And Tor is ready 48.648
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.566
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.923
Given I shutdown Tails and wait for the computer to power off 4.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.932
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.077
And Tor is ready 18.139
Then the Upgrader considers the system as up-to-date 0.385
# 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.040
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.139
After features/support/hooks.rb:326 0.799
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.895
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.495
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.146
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 19.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.587
After features/support/hooks.rb:326 0.873
After features/support/hooks.rb:100 0.000