Project Number Date
test_Tails_ISO_stable 5006 07 Aug 2024, 15: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 20:23.723 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:30.949
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.212
When I start Tails from USB drive "old" with network unplugged 1:54.166
Then the boot device has safe access rights 3.228
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.563
After features/support/hooks.rb:100 0.012
Tags: @product
2:5.897
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:21.845
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 32.643
And I take note of which tps features are available 1.610
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.492
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.182
Before features/support/hooks.rb:269 0.008
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.849
Then Tails is running from USB drive "old" 0.320
And all tps features are active 2.028
When I write some files expected to persist 1.811
# 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.459
And all persistent directories from the old Tails version have safe access rights 2.888
And I take note of which tps features are available 0.390
And I shutdown Tails and wait for the computer to power off 4.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.597
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.205
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.691
And I log in to a new session 18.653
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.665
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.188
Then the running Tails is installed on USB drive "to_upgrade" 21.167
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.119
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.397
Before features/support/hooks.rb:269 0.008
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.511
Then all tps features from the old Tails version are active 1.776
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.732
And the expected persistent files created with the old Tails version are present in the filesystem 1.391
And all persistent directories from the old Tails version have safe access rights 2.443
After features/support/hooks.rb:326 0.803
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:2.129
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.498
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.408
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.063
And Tor is ready 47.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.625
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.084
Given I shutdown Tails and wait for the computer to power off 8.780
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.501
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.316
When the network is plugged 0.076
And Tor is ready 47.322
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.589
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.608
Given I shutdown Tails and wait for the computer to power off 4.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.509
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.562
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.063
And Tor is ready 18.813
Then the Upgrader considers the system as up-to-date 0.322
# 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.577
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.981
After features/support/hooks.rb:326 0.851
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
55.963
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.581
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.830
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 44.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.000