Project Number Date
test_Tails_ISO_devel 3506 07 Sep 2024, 12:45

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:38.738 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:58.673
Before features/support/hooks.rb:269 0.005
Given a computer 0.273
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.092
And I write an old version of the Tails USB image to disk "old" 1:4.080
When I start Tails from USB drive "old" with network unplugged 1:48.604
Then the boot device has safe access rights 3.425
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:326 3.790
After features/support/hooks.rb:100 0.012
Tags: @product
2:7.070
Before features/support/hooks.rb:269 0.009
Given a computer 1.087
And I start Tails from USB drive "old" with network unplugged and I login 1:22.794
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 32.061
And I take note of which tps features are available 1.489
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.481
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.716
Before features/support/hooks.rb:269 0.006
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.062
Then Tails is running from USB drive "old" 0.360
And all tps features are active 2.082
When I write some files expected to persist 2.001
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.497
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.940
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.017
Tags: @product
2:36.946
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.823
And I log in to a new session 20.656
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.716
And I plug USB drive "to_upgrade" 2.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.783
Then the running Tails is installed on USB drive "to_upgrade" 21.038
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:326 2.244
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.762
Before features/support/hooks.rb:269 0.007
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.453
Then all tps features from the old Tails version are active 1.731
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.881
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.631
After features/support/hooks.rb:326 0.919
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:53.463
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.432
And no SquashFS delta is installed 0.259
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.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.078
And Tor is ready 23.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.900
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.283
Given I shutdown Tails and wait for the computer to power off 11.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.571
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.254
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.399
# 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.292
When the network is plugged 0.065
And Tor is ready 20.351
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.279
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.971
Given I shutdown Tails and wait for the computer to power off 4.363
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.445
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.064
And Tor is ready 16.948
Then the Upgrader considers the system as up-to-date 10.802
# 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.969
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.005
After features/support/hooks.rb:326 0.947
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
40.106
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 11.593
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
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.848
But a current signing key is available on our website 0.000
When the network is plugged 0.098
And Tor is ready 21.570
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.452
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.000