Project Number Date
test_Tails_ISO_devel 3593 20 Nov 2024, 13:08

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:33.251 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:12.118
Before features/support/hooks.rb:269 0.008
Given a computer 0.262
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.614
When I start Tails from USB drive "old" with network unplugged 1:34.745
Then the boot device has safe access rights 3.360
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 9.539
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.736
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:29.088
Then Tails is running from USB drive "old" 0.454
And I create a persistent partition 32.963
And I take note of which tps features are available 1.950
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 6.198
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.010
Tags: @product
3:7.143
Before features/support/hooks.rb:269 0.007
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.623
Then Tails is running from USB drive "old" 0.530
And all tps features are active 2.234
When I write some files expected to persist 2.072
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.481
And all persistent directories from the old Tails version have safe access rights 2.826
And I take note of which tps features are available 0.684
And I shutdown Tails and wait for the computer to power off 4.475
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.716
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.011
Tags: @product
2:37.155
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 11.799
And I log in to a new session 20.726
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.716
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.057
Then the running Tails is installed on USB drive "to_upgrade" 23.873
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.289
After features/support/hooks.rb:326 2.630
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.905
Before features/support/hooks.rb:269 0.007
Given a computer 0.542
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.531
Then all tps features from the old Tails version are active 1.936
And Tails is running from USB drive "to_upgrade" 0.489
And the boot device has safe access rights 3.342
And the expected persistent files created with the old Tails version are present in the filesystem 1.485
And all persistent directories from the old Tails version have safe access rights 2.577
After features/support/hooks.rb:326 0.655
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:56.217
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.543
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.376
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.627
When the network is plugged 0.085
And Tor is ready 24.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.765
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.826
Given I shutdown Tails and wait for the computer to power off 11.066
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.496
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.534
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.373
# 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.410
When the network is plugged 0.080
And Tor is ready 20.483
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.318
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.694
Given I shutdown Tails and wait for the computer to power off 4.412
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.596
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.565
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.082
And Tor is ready 20.328
Then the Upgrader considers the system as up-to-date 0.341
# 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.737
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.184
After features/support/hooks.rb:326 0.951
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
1:3.974
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.885
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.072
And the signing key used by the Upgrader is outdated 0.873
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 50.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.874
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.000