Project Number Date
test_Tails_ISO_devel 3594 21 Nov 2024, 12:38

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 19:58.891 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:11.245
Before features/support/hooks.rb:269 0.009
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.727
When I start Tails from USB drive "old" with network unplugged 1:33.793
Then the boot device has safe access rights 3.305
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.127
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:326 3.551
After features/support/hooks.rb:100 0.011
Tags: @product
2:14.794
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:30.830
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 32.443
And I take note of which tps features are available 1.601
Then a Tails persistence partition exists on USB drive "old" 0.896
And I shutdown Tails and wait for the computer to power off 8.483
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.728
Before features/support/hooks.rb:269 0.008
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.690
Then Tails is running from USB drive "old" 0.607
And all tps features are active 2.010
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.735
And I take note of which tps features are available 0.685
And I shutdown Tails and wait for the computer to power off 4.224
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.101
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.830
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.208
And I log in to a new session 19.212
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.287
And I plug USB drive "to_upgrade" 2.517
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.139
Then the running Tails is installed on USB drive "to_upgrade" 23.948
And I unplug USB drive "to_upgrade" 0.291
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 3.277
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.562
Before features/support/hooks.rb:269 0.008
Given a computer 0.292
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.811
Then all tps features from the old Tails version are active 1.700
And Tails is running from USB drive "to_upgrade" 0.426
And the boot device has safe access rights 4.010
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 2.688
After features/support/hooks.rb:326 0.983
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:54.562
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.499
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.378
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.078
And Tor is ready 49.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.494
Given I shutdown Tails and wait for the computer to power off 8.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.045
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 4.219
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.366
# 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.379
When the network is plugged 0.278
And Tor is ready 19.969
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.602
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.009
Given I shutdown Tails and wait for the computer to power off 4.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.857
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.063
And Tor is ready 19.626
Then the Upgrader considers the system as up-to-date 0.350
# 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.639
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.314
After features/support/hooks.rb:326 0.800
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.167
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 10.625
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.733
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 16.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.860
After features/support/hooks.rb:326 0.695
After features/support/hooks.rb:100 0.000