Project Number Date
test_Tails_ISO_devel 3675 31 Jan 2025, 17:51

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:53.355 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:9.770
Before features/support/hooks.rb:269 0.002
Given a computer 0.168
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" 32.190
When I start Tails from USB drive "old" with network unplugged 1:32.189
Then the boot device has safe access rights 3.165
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.497
After features/support/hooks.rb:100 0.005
Tags: @product
2:20.658
Before features/support/hooks.rb:269 0.002
Given a computer 0.389
And I start Tails from USB drive "old" with network unplugged and I login 1:35.244
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 33.723
And I take note of which tps features are available 1.832
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 8.316
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.015
Tags: @product
2:42.711
Before features/support/hooks.rb:269 0.003
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.950
Then Tails is running from USB drive "old" 0.583
And all tps features are active 2.378
When I write some files expected to persist 1.837
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
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.966
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 4.296
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.480
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.006
Tags: @product
2:34.293
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 10.688
And I log in to a new session 23.406
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.906
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.647
Then the running Tails is installed on USB drive "to_upgrade" 21.815
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 2.723
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.630
Before features/support/hooks.rb:269 0.003
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.832
Then all tps features from the old Tails version are active 2.092
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.959
And the expected persistent files created with the old Tails version are present in the filesystem 1.515
And all persistent directories from the old Tails version have safe access rights 2.684
After features/support/hooks.rb:326 0.639
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:16.979
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.599
And no SquashFS delta is installed 0.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.440
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.072
And Tor is ready 19.069
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.013
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.845
Given I shutdown Tails and wait for the computer to power off 8.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.612
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.225
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.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.419
# 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.427
When the network is plugged 0.071
And Tor is ready 17.954
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.404
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.065
Given I shutdown Tails and wait for the computer to power off 4.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.411
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.244
And the file system changes introduced in version 6.3~testoverlayfs are present 0.441
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.073
And Tor is ready 17.558
Then the Upgrader considers the system as up-to-date 0.349
# 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.594
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.025
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
36.309
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.594
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 18.624
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.456
After features/support/hooks.rb:326 1.179
After features/support/hooks.rb:100 0.000