Project Number Date
test_Tails_ISO_stable 5349 20 Dec 2024, 12:37

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:59.860 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:13.601
Before features/support/hooks.rb:269 0.006
Given a computer 0.329
And I create a 7200 MiB disk named "old" 0.314
And I plug USB drive "old" 1.118
And I write an old version of the Tails USB image to disk "old" 31.368
When I start Tails from USB drive "old" with network unplugged 1:36.574
Then the boot device has safe access rights 2.935
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.747
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.184
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:23.124
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 31.824
And I take note of which tps features are available 1.421
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 6.490
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.118
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.685
Then Tails is running from USB drive "old" 1.129
And all tps features are active 2.042
When I write some files expected to persist 1.645
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 3.203
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.180
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.038
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.697
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 10.538
And I log in to a new session 19.571
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.588
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.316
Then the running Tails is installed on USB drive "to_upgrade" 19.879
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.557
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.132
Before features/support/hooks.rb:269 0.004
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.121
Then all tps features from the old Tails version are active 1.555
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.001
And the expected persistent files created with the old Tails version are present in the filesystem 1.604
And all persistent directories from the old Tails version have safe access rights 2.331
After features/support/hooks.rb:326 0.624
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:11.523
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.897
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.498
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.386
When the network is plugged 0.079
And Tor is ready 20.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.532
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.968
Given I shutdown Tails and wait for the computer to power off 10.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.086
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.135
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.269
When the network is plugged 0.084
And Tor is ready 18.066
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.541
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.853
Given I shutdown Tails and wait for the computer to power off 4.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.983
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.072
And Tor is ready 14.791
Then the Upgrader considers the system as up-to-date 0.353
# 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.069
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.872
After features/support/hooks.rb:326 0.664
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
1:0.604
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.260
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.416
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 49.155
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.586
After features/support/hooks.rb:326 0.650
After features/support/hooks.rb:100 0.000