Project Number Date
test_Tails_ISO_devel 3652 16 Jan 2025, 23:10

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:11.375 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:19.646
Before features/support/hooks.rb:269 0.002
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.025
When I start Tails from USB drive "old" with network unplugged 1:42.836
Then the boot device has safe access rights 3.395
And Tails is running from USB drive "old" 0.402
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.614
After features/support/hooks.rb:100 0.006
Tags: @product
2:7.518
Before features/support/hooks.rb:269 0.002
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:24.178
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 31.735
And I take note of which tps features are available 1.657
Then a Tails persistence partition exists on USB drive "old" 0.999
And I shutdown Tails and wait for the computer to power off 8.417
After features/support/hooks.rb:326 0.201
After features/support/hooks.rb:100 0.006
Tags: @product
2:58.988
Before features/support/hooks.rb:269 0.003
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.592
Then Tails is running from USB drive "old" 0.639
And all tps features are active 2.335
When I write some files expected to persist 2.261
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.762
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.232
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.769
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.790
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.491
And I log in to a new session 19.981
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.311
And I plug USB drive "to_upgrade" 2.506
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.774
Then the running Tails is installed on USB drive "to_upgrade" 21.200
And I unplug USB drive "to_upgrade" 0.274
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:326 3.820
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.009
Before features/support/hooks.rb:269 0.004
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.419
Then all tps features from the old Tails version are active 1.765
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.706
And the expected persistent files created with the old Tails version are present in the filesystem 1.765
And all persistent directories from the old Tails version have safe access rights 2.732
After features/support/hooks.rb:326 1.111
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
7:10.461
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 12.256
And no SquashFS delta is installed 0.270
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.071
And Tor is ready 21.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.232
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.579
Given I shutdown Tails and wait for the computer to power off 13.847
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.562
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.357
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.354
When the network is plugged 0.065
And Tor is ready 20.339
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.309
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.820
Given I shutdown Tails and wait for the computer to power off 4.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.242
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.657
And the file system changes introduced in version 6.3~testoverlayfs are present 0.593
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.077
And Tor is ready 20.694
Then the Upgrader considers the system as up-to-date 0.364
# 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.315
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.241
After features/support/hooks.rb:326 0.791
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
38.960
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.702
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.149
And Tor is ready 20.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.924
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.000