Project Number Date
test_Tails_ISO_stable 5248 04 Nov 2024, 20:34

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 19:48.975 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:15.849
Before features/support/hooks.rb:269 0.005
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 30.284
When I start Tails from USB drive "old" with network unplugged 1:39.942
Then the boot device has safe access rights 3.253
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.739
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.349
Before features/support/hooks.rb:269 0.006
Given a computer 0.533
And I start Tails from USB drive "old" with network unplugged and I login 1:26.584
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 31.781
And I take note of which tps features are available 1.821
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 8.392
After features/support/hooks.rb:326 0.231
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.526
Before features/support/hooks.rb:269 0.007
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.689
Then Tails is running from USB drive "old" 0.347
And all tps features are active 2.205
When I write some files expected to persist 2.307
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.298
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.242
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.087
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.007
Tags: @product
2:34.193
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 9.843
And I log in to a new session 21.144
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.818
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.674
Then the running Tails is installed on USB drive "to_upgrade" 22.900
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 7.812
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.938
Before features/support/hooks.rb:269 0.011
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.193
Then all tps features from the old Tails version are active 1.713
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.188
And the expected persistent files created with the old Tails version are present in the filesystem 1.586
And all persistent directories from the old Tails version have safe access rights 2.684
After features/support/hooks.rb:326 1.270
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:56.691
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 15.332
And no SquashFS delta is installed 0.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
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.527
When the network is plugged 0.074
And Tor is ready 20.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.758
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.958
Given I shutdown Tails and wait for the computer to power off 14.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.067
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.377
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.436
# 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.389
When the network is plugged 0.165
And Tor is ready 48.090
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.689
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.799
Given I shutdown Tails and wait for the computer to power off 4.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.068
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.236
And the file system changes introduced in version 6.3~testoverlayfs are present 0.578
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.378
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.078
And Tor is ready 17.724
Then the Upgrader considers the system as up-to-date 0.380
# 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 15.281
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.858
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
39.426
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.819
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 21.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.560
After features/support/hooks.rb:326 0.697
After features/support/hooks.rb:100 0.000