Project Number Date
test_Tails_ISO_stable 5048 27 Aug 2024, 08:48

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:49.272 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:35.738
Before features/support/hooks.rb:269 0.008
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 30.148
When I start Tails from USB drive "old" with network unplugged 1:59.420
Then the boot device has safe access rights 3.593
And Tails is running from USB drive "old" 0.459
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.128
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 7.186
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.007
Before features/support/hooks.rb:269 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:26.853
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 32.543
And I take note of which tps features are available 2.043
Then a Tails persistence partition exists on USB drive "old" 0.971
And I shutdown Tails and wait for the computer to power off 9.031
After features/support/hooks.rb:326 0.258
After features/support/hooks.rb:100 0.015
Tags: @product
2:58.553
Before features/support/hooks.rb:269 0.011
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.118
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.209
When I write some files expected to persist 3.460
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
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.565
And I take note of which tps features are available 0.530
And I shutdown Tails and wait for the computer to power off 4.671
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.716
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.022
Tags: @product
2:35.859
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.480
And I log in to a new session 19.730
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.888
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.670
Then the running Tails is installed on USB drive "to_upgrade" 23.242
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 2.656
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.894
Before features/support/hooks.rb:269 0.007
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.024
Then all tps features from the old Tails version are active 1.864
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.377
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.547
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:57.133
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 23.801
And no SquashFS delta is installed 0.190
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.489
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.084
And Tor is ready 23.296
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.037
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.476
Given I shutdown Tails and wait for the computer to power off 10.907
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.641
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.699
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
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.350
# 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.289
When the network is plugged 0.099
And Tor is ready 21.892
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.796
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.938
Given I shutdown Tails and wait for the computer to power off 4.606
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.611
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.188
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.083
And Tor is ready 20.757
Then the Upgrader considers the system as up-to-date 10.935
# 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.612
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.921
After features/support/hooks.rb:326 1.058
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
1:0.086
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 11.490
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.857
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 46.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.585
After features/support/hooks.rb:326 0.667
After features/support/hooks.rb:100 0.000