Project Number Date
test_Tails_ISO_stable 4712 12 Mar 2024, 18: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 18:57.421 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:39.989
Before features/support/hooks.rb:245 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 18.998
When I start Tails from USB drive "old" with network unplugged 1:14.471
Then the boot device has safe access rights 4.315
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:291 3.781
After features/support/hooks.rb:75 0.010
Tags: @product
2:13.439
Before features/support/hooks.rb:245 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:22.065
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 40.402
And I take note of which tps features are available 1.772
Then a Tails persistence partition exists on USB drive "old" 0.708
And I shutdown Tails and wait for the computer to power off 8.026
After features/support/hooks.rb:291 0.140
After features/support/hooks.rb:75 0.009
Tags: @product
2:47.490
Before features/support/hooks.rb:245 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.331
Then Tails is running from USB drive "old" 0.388
And all tps features are active 1.982
When I write some files expected to persist 1.864
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
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.885
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 4.018
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.723
After features/support/hooks.rb:291 0.129
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.945
Before features/support/hooks.rb:245 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.494
And I log in to a new session 16.491
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.627
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.327
Then the running Tails is installed on USB drive "to_upgrade" 15.117
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:291 2.106
After features/support/hooks.rb:75 0.000
Tags: @product
2:24.715
Before features/support/hooks.rb:245 0.007
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.312
Then all tps features from the old Tails version are active 1.488
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.296
And the expected persistent files created with the old Tails version are present in the filesystem 1.484
And all persistent directories from the old Tails version have safe access rights 2.600
After features/support/hooks.rb:291 0.629
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:46.677
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.197
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
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.455
When the network is plugged 0.039
And Tor is ready 18.771
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.306
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.995
Given I shutdown Tails and wait for the computer to power off 7.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.409
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 3.812
And the file system changes introduced in version 6.2~testoverlayfs are present 0.424
And only the 6.2~testoverlayfs SquashFS delta is installed 0.140
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.385
When the network is plugged 0.042
And Tor is ready 17.454
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.507
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.338
Given I shutdown Tails and wait for the computer to power off 5.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.134
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.953
And the file system changes introduced in version 6.3~testoverlayfs are present 0.578
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.046
And Tor is ready 16.380
Then the Upgrader considers the system as up-to-date 0.238
# 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 14.248
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.888
After features/support/hooks.rb:291 0.687
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
30.163
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.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.610
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 16.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.381
After features/support/hooks.rb:291 1.072
After features/support/hooks.rb:75 0.000