Project Number Date
test_Tails_ISO_stable 5118 25 Sep 2024, 12:09

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 18:40.059 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
1:58.052
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.140
When I start Tails from USB drive "old" with network unplugged 1:23.715
Then the boot device has safe access rights 2.924
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.546
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.303
Before features/support/hooks.rb:269 0.006
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:20.657
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 31.609
And I take note of which tps features are available 1.442
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 8.302
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.694
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.006
Then Tails is running from USB drive "old" 0.571
And all tps features are active 1.943
When I write some files expected to persist 1.562
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.379
And all persistence configuration files have safe access rights 0.568
And all persistent directories from the old Tails version have safe access rights 2.730
And I take note of which tps features are available 0.393
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.036
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.083
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 10.917
And I log in to a new session 17.411
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.940
And I plug USB drive "to_upgrade" 2.373
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.407
Then the running Tails is installed on USB drive "to_upgrade" 19.625
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:326 2.017
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.506
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.514
Then all tps features from the old Tails version are active 1.522
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 3.078
And the expected persistent files created with the old Tails version are present in the filesystem 1.263
And all persistent directories from the old Tails version have safe access rights 2.652
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:48.160
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.995
And no SquashFS delta is installed 0.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.431
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.069
And Tor is ready 22.908
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.111
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.239
Given I shutdown Tails and wait for the computer to power off 8.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.374
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.236
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
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.305
# 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.253
When the network is plugged 0.063
And Tor is ready 17.668
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.129
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.922
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.354
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.865
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.073
And Tor is ready 46.817
Then the Upgrader considers the system as up-to-date 0.288
# 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.808
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.028
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.258
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 9.786
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.676
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 17.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.337
After features/support/hooks.rb:326 0.803
After features/support/hooks.rb:100 0.000