Project Number Date
test_Tails_ISO_devel 3632 04 Jan 2025, 12:29

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:58.530 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:6.096
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.013
When I start Tails from USB drive "old" with network unplugged 1:28.667
Then the boot device has safe access rights 3.085
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.475
After features/support/hooks.rb:100 0.014
Tags: @product
1:58.733
Before features/support/hooks.rb:269 0.007
Given a computer 0.418
And I start Tails from USB drive "old" with network unplugged and I login 1:17.156
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 30.287
And I take note of which tps features are available 1.378
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.329
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.880
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.697
Then Tails is running from USB drive "old" 0.354
And all tps features are active 2.180
When I write some files expected to persist 1.630
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.421
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 4.342
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.011
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.079
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 11.799
And I log in to a new session 19.076
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.714
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.866
Then the running Tails is installed on USB drive "to_upgrade" 23.769
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 3.550
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.806
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.146
Then all tps features from the old Tails version are active 1.782
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.361
And the expected persistent files created with the old Tails version are present in the filesystem 1.503
And all persistent directories from the old Tails version have safe access rights 2.486
After features/support/hooks.rb:326 0.618
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:29.541
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.662
And no SquashFS delta is installed 0.791
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.401
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.092
And Tor is ready 23.432
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.344
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.602
Given I shutdown Tails and wait for the computer to power off 10.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.092
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.184
And the file system changes introduced in version 6.2~testoverlayfs are present 0.462
And only the 6.2~testoverlayfs SquashFS delta is installed 0.134
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.315
When the network is plugged 0.079
And Tor is ready 19.804
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.187
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.272
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.110
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.044
And the file system changes introduced in version 6.3~testoverlayfs are present 0.687
And only the 6.3~testoverlayfs SquashFS delta is installed 0.120
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.396
When the network is plugged 0.089
And Tor is ready 21.137
Then the Upgrader considers the system as up-to-date 0.316
# 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.150
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.005
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.391
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.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.361
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 20.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.384
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.000