Project Number Date
test_Tails_ISO_devel 3351 16 Apr 2024, 15:45

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:10.185 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:40.956
Before features/support/hooks.rb:245 0.007
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 20.573
When I start Tails from USB drive "old" with network unplugged 1:15.044
Then the boot device has safe access rights 3.040
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:291 3.762
After features/support/hooks.rb:75 0.010
Tags: @product
2:4.591
Before features/support/hooks.rb:245 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:16.774
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 35.953
And I take note of which tps features are available 1.327
Then a Tails persistence partition exists on USB drive "old" 1.322
And I shutdown Tails and wait for the computer to power off 8.662
After features/support/hooks.rb:291 0.216
After features/support/hooks.rb:75 0.013
Tags: @product
2:34.616
Before features/support/hooks.rb:245 0.008
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.542
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.130
When I write some files expected to persist 1.637
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.685
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 4.631
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.298
After features/support/hooks.rb:291 0.143
After features/support/hooks.rb:75 0.011
Tags: @product
2:22.895
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 10.682
And I log in to a new session 18.116
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.405
And I plug USB drive "to_upgrade" 2.578
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.081
Then the running Tails is installed on USB drive "to_upgrade" 14.602
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:291 3.595
After features/support/hooks.rb:75 0.000
Tags: @product
2:11.608
Before features/support/hooks.rb:245 0.009
Given a computer 0.287
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.851
Then all tps features from the old Tails version are active 1.699
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.502
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.476
After features/support/hooks.rb:291 0.706
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:19.129
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.653
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
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.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.042
And Tor is ready 17.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.541
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.412
Given I shutdown Tails and wait for the computer to power off 9.068
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.582
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.921
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.273
When the network is plugged 0.105
And Tor is ready 17.641
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.895
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.043
Given I shutdown Tails and wait for the computer to power off 4.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.453
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.158
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.051
And Tor is ready 16.603
Then the Upgrader considers the system as up-to-date 10.729
# 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.283
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.890
After features/support/hooks.rb:291 0.847
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
56.387
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.533
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.512
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 44.402
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
After features/support/hooks.rb:291 1.128
After features/support/hooks.rb:75 0.000