Project Number Date
test_Tails_ISO_stable 5457 14 Feb 2025, 08:48

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:51.582 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:57.402
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 27.532
When I start Tails from USB drive "old" with network unplugged 1:24.497
Then the boot device has safe access rights 2.998
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 3.524
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.910
Before features/support/hooks.rb:269 0.004
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:30.251
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 32.441
And I take note of which tps features are available 1.418
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.400
After features/support/hooks.rb:326 0.207
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.579
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.221
Then Tails is running from USB drive "old" 1.627
And all tps features are active 2.015
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.348
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.667
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.268
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.491
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.680
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.416
And I log in to a new session 19.483
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.522
And I plug USB drive "to_upgrade" 2.608
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.198
Then the running Tails is installed on USB drive "to_upgrade" 25.034
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 2.258
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.303
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.962
Then all tps features from the old Tails version are active 1.620
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.337
And the expected persistent files created with the old Tails version are present in the filesystem 1.504
And all persistent directories from the old Tails version have safe access rights 2.340
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:10.960
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 12.198
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.089
And Tor is ready 20.078
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.951
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.333
Given I shutdown Tails and wait for the computer to power off 8.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.441
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.438
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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.290
When the network is plugged 0.070
And Tor is ready 17.623
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.559
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.772
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.806
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.133
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.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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.088
And Tor is ready 16.424
Then the Upgrader considers the system as up-to-date 0.302
# 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.265
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.855
After features/support/hooks.rb:326 0.886
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
37.745
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.363
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.715
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 19.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.662
After features/support/hooks.rb:326 0.915
After features/support/hooks.rb:100 0.000