Project Number Date
test_Tails_ISO_devel 3232 11 Jan 2024, 21:59

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.638 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:45.804
Before features/support/hooks.rb:245 0.006
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.090
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 40.551
When I start Tails from USB drive "old" with network unplugged 59.902
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:291 3.697
After features/support/hooks.rb:75 0.010
Tags: @product
2:4.945
Before features/support/hooks.rb:245 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:9.071
Then Tails is running from USB drive "old" 0.537
And I create a persistent partition 44.445
And I take note of which tps features are available 1.545
Then a Tails persistence partition exists on USB drive "old" 0.891
And I shutdown Tails and wait for the computer to power off 8.235
After features/support/hooks.rb:291 0.134
After features/support/hooks.rb:75 0.014
Tags: @product
2:19.400
Before features/support/hooks.rb:245 0.008
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.754
Then Tails is running from USB drive "old" 0.401
And all tps features are active 2.135
When I write some files expected to persist 1.845
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.685
And all persistent directories from the old Tails version have safe access rights 2.789
And I take note of which tps features are available 0.554
And I shutdown Tails and wait for the computer to power off 3.059
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.724
After features/support/hooks.rb:291 0.147
After features/support/hooks.rb:75 0.010
Tags: @product
2:48.703
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 23.316
And I log in to a new session 16.412
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.293
And I plug USB drive "to_upgrade" 2.542
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.273
Then the running Tails is installed on USB drive "to_upgrade" 15.474
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:291 0.813
After features/support/hooks.rb:75 0.000
Tags: @product
2:7.854
Before features/support/hooks.rb:245 0.008
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.632
Then all tps features from the old Tails version are active 1.728
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.495
And the expected persistent files created with the old Tails version are present in the filesystem 1.803
And all persistent directories from the old Tails version have safe access rights 2.641
After features/support/hooks.rb:291 0.798
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:33.916
Before features/support/hooks.rb:245 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.755
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.882
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.314
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.457
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.559
When the network is plugged 0.045
And Tor is ready 46.325
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.576
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.089
Given I shutdown Tails and wait for the computer to power off 6.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.426
Then Tails is running version 2.2~testoverlayfsng 0.111
And all tps features are active 2.417
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.396
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.277
When the network is plugged 0.043
And Tor is ready 16.267
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.657
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.348
Given I shutdown Tails and wait for the computer to power off 4.226
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.166
Then Tails is running version 2.3~testoverlayfsng 0.168
And all tps features are active 2.479
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.743
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.377
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.400
When the network is plugged 0.044
And Tor is ready 16.060
Then the Upgrader considers the system as up-to-date 0.311
# 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 25.373
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.752
After features/support/hooks.rb:291 0.827
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
30.012
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.907
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.441
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.091
And the signing key used by the Upgrader is outdated 1.384
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 15.299
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.830
After features/support/hooks.rb:291 0.932
After features/support/hooks.rb:75 0.000