Project Number Date
test_Tails_ISO_stable 4908 21 Jun 2024, 12:27

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:43.113 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:1.715
Before features/support/hooks.rb:269 0.006
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.518
When I start Tails from USB drive "old" with network unplugged 1:26.824
Then the boot device has safe access rights 3.045
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.539
After features/support/hooks.rb:100 0.022
Tags: @product
2:15.894
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:29.432
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 35.100
And I take note of which tps features are available 1.537
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 8.475
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.626
Before features/support/hooks.rb:269 0.008
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.164
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.030
When I write some files expected to persist 1.637
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.331
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 4.292
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.469
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.166
Before features/support/hooks.rb:269 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 12.451
And I log in to a new session 17.603
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.645
And I plug USB drive "to_upgrade" 2.473
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.965
Then the running Tails is installed on USB drive "to_upgrade" 16.611
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 4.607
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.612
Before features/support/hooks.rb:269 0.008
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.008
Then all tps features from the old Tails version are active 1.624
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.582
And the expected persistent files created with the old Tails version are present in the filesystem 1.444
And all persistent directories from the old Tails version have safe access rights 2.368
After features/support/hooks.rb:326 1.005
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:23.622
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 10.613
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.034
And Tor is ready 17.618
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.797
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.209
Given I shutdown Tails and wait for the computer to power off 8.610
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.331
Then Tails is running version 6.2~testoverlayfs 0.034
And all tps features are active 2.263
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.286
When the network is plugged 0.041
And Tor is ready 21.242
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.929
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.586
Given I shutdown Tails and wait for the computer to power off 4.440
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.450
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.271
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.042
And Tor is ready 19.473
Then the Upgrader considers the system as up-to-date 0.328
# 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 13.915
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.891
After features/support/hooks.rb:326 0.822
After features/support/hooks.rb:100 0.124
Tags: @product @automatic_upgrade
35.476
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 9.750
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.675
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 16.678
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.860
After features/support/hooks.rb:326 0.814
After features/support/hooks.rb:100 0.000