Project Number Date
test_Tails_ISO_stable 5024 13 Aug 2024, 12:48

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 20:31.021 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:58.726
Before features/support/hooks.rb:269 0.008
Given a computer 0.292
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 58.642
When I start Tails from USB drive "old" with network unplugged 1:54.269
Then the boot device has safe access rights 3.283
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.094
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.786
After features/support/hooks.rb:100 0.014
Tags: @product
2:17.527
Before features/support/hooks.rb:269 0.009
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:29.711
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 36.206
And I take note of which tps features are available 1.959
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.225
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.792
Before features/support/hooks.rb:269 0.008
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.349
Then Tails is running from USB drive "old" 0.368
And all tps features are active 2.208
When I write some files expected to persist 1.864
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 3.212
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.066
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.308
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.013
Tags: @product
2:39.068
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.517
And I log in to a new session 18.516
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.403
And I plug USB drive "to_upgrade" 2.440
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.350
Then the running Tails is installed on USB drive "to_upgrade" 20.390
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 3.772
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.065
Before features/support/hooks.rb:269 0.011
Given a computer 1.529
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.856
Then all tps features from the old Tails version are active 1.777
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.262
And the expected persistent files created with the old Tails version are present in the filesystem 1.463
And all persistent directories from the old Tails version have safe access rights 2.832
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:43.761
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 27.037
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.428
And Tor is ready 18.757
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.638
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.434
Given I shutdown Tails and wait for the computer to power off 8.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.199
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.481
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
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.307
# 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.265
When the network is plugged 0.081
And Tor is ready 16.991
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.873
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.342
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.081
Then Tails is running version 6.3~testoverlayfs 0.074
And all tps features are active 5.595
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.070
And Tor is ready 15.040
Then the Upgrader considers the system as up-to-date 0.343
# 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.578
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.026
After features/support/hooks.rb:326 0.910
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
39.081
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.250
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.791
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 20.216
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.285
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.000