Project Number Date
test_Tails_ISO_devel 3212 25 Dec 2023, 17:47

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 16:32.668 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:17.834
Before features/support/hooks.rb:245 0.006
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 17.792
When I start Tails from USB drive "old" with network unplugged 55.020
Then the boot device has safe access rights 2.865
And Tails is running from USB drive "old" 0.278
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:291 3.446
After features/support/hooks.rb:75 0.008
Tags: @product
1:54.982
Before features/support/hooks.rb:245 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:1.694
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 43.072
And I take note of which tps features are available 1.510
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 7.234
After features/support/hooks.rb:291 0.148
After features/support/hooks.rb:75 0.009
Tags: @product
2:17.635
Before features/support/hooks.rb:245 0.006
Given a computer 1.003
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:48.854
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.056
When I write some files expected to persist 1.874
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.674
And all persistent directories from the old Tails version have safe access rights 2.821
And I take note of which tps features are available 0.629
And I shutdown Tails and wait for the computer to power off 4.143
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.949
After features/support/hooks.rb:291 0.112
After features/support/hooks.rb:75 0.012
Tags: @product
2:32.046
Before features/support/hooks.rb:245 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 11.181
And I log in to a new session 16.128
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.254
And I plug USB drive "to_upgrade" 2.594
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.059
Then the running Tails is installed on USB drive "to_upgrade" 12.445
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:291 1.011
After features/support/hooks.rb:75 0.000
Tags: @product
1:57.221
Before features/support/hooks.rb:245 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.709
Then all tps features from the old Tails version are active 1.747
And Tails is running from USB drive "to_upgrade" 0.379
And the boot device has safe access rights 3.641
And the expected persistent files created with the old Tails version are present in the filesystem 1.670
And all persistent directories from the old Tails version have safe access rights 2.888
After features/support/hooks.rb:291 0.644
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:3.234
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.024
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.415
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.075
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.379
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.523
When the network is plugged 0.032
And Tor is ready 18.690
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.632
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.894
Given I shutdown Tails and wait for the computer to power off 15.124
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.809
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 2.296
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.415
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.299
When the network is plugged 0.062
And Tor is ready 14.678
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.664
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.410
Given I shutdown Tails and wait for the computer to power off 4.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.236
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 2.724
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.559
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.302
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.303
When the network is plugged 0.042
And Tor is ready 15.250
Then the Upgrader considers the system as up-to-date 10.793
# 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 24.866
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.637
After features/support/hooks.rb:291 0.897
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
29.712
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.795
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.073
And the signing key used by the Upgrader is outdated 0.703
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 15.910
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.805
After features/support/hooks.rb:291 0.714
After features/support/hooks.rb:75 0.000