Project Number Date
test_Tails_ISO_stable 5192 17 Oct 2024, 15:08

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.802 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:4.802
Before features/support/hooks.rb:269 0.004
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.937
When I start Tails from USB drive "old" with network unplugged 1:29.255
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.379
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:326 3.533
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.451
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:29.539
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 35.831
And I take note of which tps features are available 1.494
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 8.296
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.007
Tags: @product
3:0.212
Before features/support/hooks.rb:269 0.003
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.126
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.440
When I write some files expected to persist 1.770
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.869
And I take note of which tps features are available 0.595
And I shutdown Tails and wait for the computer to power off 4.383
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.825
After features/support/hooks.rb:326 0.115
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.904
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.343
And I log in to a new session 18.511
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.699
And I plug USB drive "to_upgrade" 2.394
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.937
Then the running Tails is installed on USB drive "to_upgrade" 19.484
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.282
After features/support/hooks.rb:326 2.085
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.195
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.508
Then all tps features from the old Tails version are active 3.407
And Tails is running from USB drive "to_upgrade" 0.385
And the boot device has safe access rights 3.869
And the expected persistent files created with the old Tails version are present in the filesystem 1.910
And all persistent directories from the old Tails version have safe access rights 2.889
After features/support/hooks.rb:326 1.459
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:51.102
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.101
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.127
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.366
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.615
When the network is plugged 0.072
And Tor is ready 20.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.510
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.791
Given I shutdown Tails and wait for the computer to power off 8.721
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.203
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.690
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.427
# 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.311
When the network is plugged 0.080
And Tor is ready 20.011
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.455
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.210
Given I shutdown Tails and wait for the computer to power off 4.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.773
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.543
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.088
And Tor is ready 20.687
Then the Upgrader considers the system as up-to-date 0.339
# 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.113
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.042
After features/support/hooks.rb:326 0.849
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.132
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 10.972
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.080
But a current signing key is available on our website 0.000
When the network is plugged 0.175
And Tor is ready 19.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.444
After features/support/hooks.rb:326 0.954
After features/support/hooks.rb:100 0.000