Project Number Date
test_Tails_ISO_stable 5564 10 Apr 2025, 13:24

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:0.170 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:10.053
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 34.483
When I start Tails from USB drive "old" with network unplugged 1:30.256
Then the boot device has safe access rights 3.122
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:330 3.751
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.428
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:28.155
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 32.266
And I take note of which tps features are available 2.219
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.407
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.529
Then Tails is running from USB drive "old" 0.391
And all tps features are active 1.760
When I write some files expected to persist 1.622
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.900
And I take note of which tps features are available 0.406
And I shutdown Tails and wait for the computer to power off 4.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.127
After features/support/hooks.rb:330 0.104
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.890
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.176
And I log in to a new session 19.447
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.790
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.764
Then the running Tails is installed on USB drive "to_upgrade" 25.818
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 6.639
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.124
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.289
Then all tps features from the old Tails version are active 1.738
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.475
And the expected persistent files created with the old Tails version are present in the filesystem 1.427
And all persistent directories from the old Tails version have safe access rights 2.619
After features/support/hooks.rb:330 1.421
After features/support/hooks.rb:100 0.079
Tags: @product @automatic_upgrade
7:1.274
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.675
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.576
When the network is plugged 0.109
And Tor is ready 22.603
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.534
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.022
Given I shutdown Tails and wait for the computer to power off 10.763
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.336
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.118
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.293
When the network is plugged 0.060
And Tor is ready 18.659
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.954
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.111
Given I shutdown Tails and wait for the computer to power off 4.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.632
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.162
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.087
And Tor is ready 44.409
Then the Upgrader considers the system as up-to-date 0.307
# 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 16.443
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.072
After features/support/hooks.rb:330 1.053
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.564
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.118
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 20.550
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.513
After features/support/hooks.rb:330 0.893
After features/support/hooks.rb:100 0.000