Project Number Date
test_Tails_ISO_stable 4537 28 Nov 2023, 00:12

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 16:9.578 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:24.725
Before features/support/hooks.rb:245 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 19.263
When I start Tails from USB drive "old" with network unplugged 1:0.504
Then the boot device has safe access rights 2.858
And Tails is running from USB drive "old" 0.287
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:291 3.727
After features/support/hooks.rb:75 0.010
Tags: @product
1:54.943
Before features/support/hooks.rb:245 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:2.435
Then Tails is running from USB drive "old" 0.384
And I create a persistent partition 42.533
And I take note of which tps features are available 1.357
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 7.190
After features/support/hooks.rb:291 0.132
After features/support/hooks.rb:75 0.010
Tags: @product
2:14.531
Before features/support/hooks.rb:245 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:48.140
Then Tails is running from USB drive "old" 0.386
And all tps features are active 2.153
When I write some files expected to persist 1.921
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.659
And all persistent directories from the old Tails version have safe access rights 2.520
And I take note of which tps features are available 0.519
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.753
After features/support/hooks.rb:291 0.131
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.837
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.180
And I log in to a new session 15.525
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.352
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.804
Then the running Tails is installed on USB drive "to_upgrade" 13.118
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 3.560
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.347
Before features/support/hooks.rb:245 0.007
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.715
Then all tps features from the old Tails version are active 1.810
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.819
And the expected persistent files created with the old Tails version are present in the filesystem 1.623
And all persistent directories from the old Tails version have safe access rights 2.875
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:38.231
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 11.121
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.346
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.079
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.357
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.562
When the network is plugged 0.039
And Tor is ready 19.741
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.584
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.767
Given I shutdown Tails and wait for the computer to power off 6.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.250
Then Tails is running version 2.2~testoverlayfsng 0.145
And all tps features are active 2.361
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.360
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.288
# 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.282
When the network is plugged 0.064
And Tor is ready 15.162
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.737
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.548
Given I shutdown Tails and wait for the computer to power off 3.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.719
Then Tails is running version 2.3~testoverlayfsng 0.128
And all tps features are active 2.012
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.583
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.074
# 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.299
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.293
When the network is plugged 0.037
And Tor is ready 14.054
Then the Upgrader considers the system as up-to-date 0.269
# 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 24.712
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.476
After features/support/hooks.rb:291 0.740
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
26.961
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 9.541
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.347
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the signing key used by the Upgrader is outdated 0.517
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 12.846
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.607
After features/support/hooks.rb:291 0.765
After features/support/hooks.rb:75 0.000