Project Number Date
test_Tails_ISO_devel 3659 23 Jan 2025, 17:50

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:15.275 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
1:55.796
Before features/support/hooks.rb:269 0.002
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 27.523
When I start Tails from USB drive "old" with network unplugged 1:23.119
Then the boot device has safe access rights 2.885
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.556
After features/support/hooks.rb:100 0.048
Tags: @product
2:3.791
Before features/support/hooks.rb:269 0.003
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:21.320
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 31.387
And I take note of which tps features are available 1.505
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 8.260
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.006
Tags: @product
2:49.320
Before features/support/hooks.rb:269 0.002
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.357
Then Tails is running from USB drive "old" 0.410
And all tps features are active 2.024
When I write some files expected to persist 2.229
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.662
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.262
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.160
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.005
Tags: @product
2:28.338
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.968
And I log in to a new session 19.221
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.365
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.830
Then the running Tails is installed on USB drive "to_upgrade" 22.097
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.256
After features/support/hooks.rb:326 2.295
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.544
Before features/support/hooks.rb:269 0.003
Given a computer 0.162
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.908
Then all tps features from the old Tails version are active 1.697
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.464
And the expected persistent files created with the old Tails version are present in the filesystem 1.525
And all persistent directories from the old Tails version have safe access rights 2.469
After features/support/hooks.rb:326 0.745
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:7.502
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.177
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.532
When the network is plugged 0.070
And Tor is ready 25.942
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.167
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.068
Given I shutdown Tails and wait for the computer to power off 10.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.984
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
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.339
# 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.331
When the network is plugged 0.071
And Tor is ready 18.253
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.918
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.374
Given I shutdown Tails and wait for the computer to power off 4.346
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.491
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.116
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.120
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.088
And Tor is ready 19.755
Then the Upgrader considers the system as up-to-date 0.314
# 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 15.079
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
37.981
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.578
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.438
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 22.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.507
After features/support/hooks.rb:326 1.004
After features/support/hooks.rb:100 0.000