Project Number Date
test_Tails_ISO_stable 4926 09 Jul 2024, 18:22

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.325 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:23.017
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.711
When I start Tails from USB drive "old" with network unplugged 1:47.232
Then the boot device has safe access rights 2.823
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.526
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.767
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:29.201
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 31.471
And I take note of which tps features are available 1.433
Then a Tails persistence partition exists on USB drive "old" 0.860
And I shutdown Tails and wait for the computer to power off 8.301
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.571
Before features/support/hooks.rb:269 0.007
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.553
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.833
When I write some files expected to persist 1.575
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.648
And I take note of which tps features are available 0.534
And I shutdown Tails and wait for the computer to power off 4.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.908
After features/support/hooks.rb:326 0.087
After features/support/hooks.rb:100 0.010
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 9.876
And I log in to a new session 17.074
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.560
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.090
Then the running Tails is installed on USB drive "to_upgrade" 19.653
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 3.535
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.639
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.296
Then all tps features from the old Tails version are active 1.626
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.493
And the expected persistent files created with the old Tails version are present in the filesystem 1.244
And all persistent directories from the old Tails version have safe access rights 2.433
After features/support/hooks.rb:326 0.610
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:11.518
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.115
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.038
And Tor is ready 17.032
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.612
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.934
Given I shutdown Tails and wait for the computer to power off 8.908
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.902
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.321
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
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.325
# 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.242
When the network is plugged 0.037
And Tor is ready 17.438
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.140
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.237
Given I shutdown Tails and wait for the computer to power off 4.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.406
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.093
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.330
When the network is plugged 0.051
And Tor is ready 16.318
Then the Upgrader considers the system as up-to-date 10.740
# 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.297
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.962
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.727
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.877
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 1.321
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 18.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.792
After features/support/hooks.rb:326 0.643
After features/support/hooks.rb:100 0.000