Project Number Date
test_Tails_ISO_stable 5078 07 Sep 2024, 12:25

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:41.054 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:21.740
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 37.149
When I start Tails from USB drive "old" with network unplugged 1:38.808
Then the boot device has safe access rights 3.417
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.256
After features/support/hooks.rb:326 3.562
After features/support/hooks.rb:100 0.026
Tags: @product
2:4.930
Before features/support/hooks.rb:269 0.004
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:21.521
Then Tails is running from USB drive "old" 0.413
And I create a persistent partition 32.150
And I take note of which tps features are available 1.372
Then a Tails persistence partition exists on USB drive "old" 0.883
And I shutdown Tails and wait for the computer to power off 8.395
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.991
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.613
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.617
When I write some files expected to persist 1.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 2.866
And I take note of which tps features are available 0.526
And I shutdown Tails and wait for the computer to power off 4.226
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.107
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.920
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 13.363
And I log in to a new session 22.067
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.575
And I plug USB drive "to_upgrade" 2.557
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.198
Then the running Tails is installed on USB drive "to_upgrade" 20.746
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.960
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.862
Before features/support/hooks.rb:269 0.010
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.969
Then all tps features from the old Tails version are active 1.765
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.557
And the expected persistent files created with the old Tails version are present in the filesystem 1.477
And all persistent directories from the old Tails version have safe access rights 2.529
After features/support/hooks.rb:326 0.912
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:37.261
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.477
And no SquashFS delta is installed 0.267
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.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.355
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.091
And Tor is ready 22.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.761
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.275
Given I shutdown Tails and wait for the computer to power off 11.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.867
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.229
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.330
When the network is plugged 0.083
And Tor is ready 18.298
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.732
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.669
Given I shutdown Tails and wait for the computer to power off 4.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.903
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.063
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.587
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.408
When the network is plugged 0.099
And Tor is ready 21.539
Then the Upgrader considers the system as up-to-date 0.330
# 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.397
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.217
After features/support/hooks.rb:326 0.976
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.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.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.534
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.095
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.577
After features/support/hooks.rb:326 1.282
After features/support/hooks.rb:100 0.000