Project Number Date
test_Tails_ISO_stable 5324 10 Dec 2024, 08:30

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:20.617 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:24.439
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
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" 30.416
When I start Tails from USB drive "old" with network unplugged 1:48.520
Then the boot device has safe access rights 3.149
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 3.585
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.866
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:23.291
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 31.493
And I take note of which tps features are available 1.412
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.346
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.942
Before features/support/hooks.rb:269 0.005
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.916
Then Tails is running from USB drive "old" 0.994
And all tps features are active 2.095
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.890
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 4.384
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.673
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.432
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.734
And I log in to a new session 24.874
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.695
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.202
Then the running Tails is installed on USB drive "to_upgrade" 24.071
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 2.649
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.345
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.927
Then all tps features from the old Tails version are active 1.588
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.365
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 2.465
After features/support/hooks.rb:326 0.817
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:26.224
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 13.270
And no SquashFS delta is installed 0.321
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.061
And Tor is ready 20.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.830
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.011
Given I shutdown Tails and wait for the computer to power off 10.916
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.256
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.320
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.266
When the network is plugged 0.063
And Tor is ready 19.465
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.042
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.523
Given I shutdown Tails and wait for the computer to power off 4.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.635
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 2.093
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.393
When the network is plugged 0.082
And Tor is ready 17.475
Then the Upgrader considers the system as up-to-date 0.315
# 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.156
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.116
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.366
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.330
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the signing key used by the Upgrader is outdated 1.655
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 18.426
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.364
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.000