Project Number Date
test_Tails_ISO_stable 5400 17 Jan 2025, 08:35

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:53.500 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:8.061
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.224
When I start Tails from USB drive "old" with network unplugged 1:32.255
Then the boot device has safe access rights 2.928
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.432
And I unplug USB drive "old" 0.459
After features/support/hooks.rb:326 3.734
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.772
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:20.691
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 30.952
And I take note of which tps features are available 1.591
Then a Tails persistence partition exists on USB drive "old" 0.752
And I shutdown Tails and wait for the computer to power off 8.271
After features/support/hooks.rb:326 0.133
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.385
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.364
Then Tails is running from USB drive "old" 0.329
And all tps features are active 1.824
When I write some files expected to persist 1.739
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.315
And I take note of which tps features are available 0.559
And I shutdown Tails and wait for the computer to power off 4.562
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.857
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.221
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.349
And I log in to a new session 18.663
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.451
And I plug USB drive "to_upgrade" 2.342
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.784
Then the running Tails is installed on USB drive "to_upgrade" 16.190
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.060
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.359
Before features/support/hooks.rb:269 0.004
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.073
Then all tps features from the old Tails version are active 1.611
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.364
And the expected persistent files created with the old Tails version are present in the filesystem 1.385
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:326 1.033
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:40.543
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 12.476
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
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.835
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.068
And Tor is ready 22.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.327
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.603
Given I shutdown Tails and wait for the computer to power off 1:18.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.638
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.201
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.281
# 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.260
When the network is plugged 0.088
And Tor is ready 19.869
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.121
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.169
Given I shutdown Tails and wait for the computer to power off 4.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.519
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.990
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.381
When the network is plugged 0.068
And Tor is ready 18.816
Then the Upgrader considers the system as up-to-date 10.774
# 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.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.914
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.156
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.997
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 21.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.183
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.000