Project Number Date
test_Tails_ISO_stable 4885 11 Jun 2024, 19:58

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:36.696 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:15.538
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 35.723
When I start Tails from USB drive "old" with network unplugged 1:34.165
Then the boot device has safe access rights 3.238
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.413
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:320 3.566
After features/support/hooks.rb:100 0.016
Tags: @product
2:18.530
Before features/support/hooks.rb:269 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:31.595
Then Tails is running from USB drive "old" 0.427
And I create a persistent partition 34.420
And I take note of which tps features are available 2.207
Then a Tails persistence partition exists on USB drive "old" 0.910
And I shutdown Tails and wait for the computer to power off 8.752
After features/support/hooks.rb:320 0.257
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.847
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.876
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.611
When I write some files expected to persist 1.894
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.519
And all persistent directories from the old Tails version have safe access rights 2.633
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 4.565
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.410
After features/support/hooks.rb:320 0.169
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.500
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.142
And I log in to a new session 19.013
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.538
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.795
Then the running Tails is installed on USB drive "to_upgrade" 24.121
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:320 2.452
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.520
Before features/support/hooks.rb:269 0.008
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.239
Then all tps features from the old Tails version are active 1.825
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.761
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.629
After features/support/hooks.rb:320 0.656
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:36.021
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.025
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
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.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.214
And Tor is ready 19.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.684
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.522
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:9.621
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.150
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
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.408
# 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.279
When the network is plugged 0.044
And Tor is ready 18.593
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.251
Given I shutdown Tails and wait for the computer to power off 4.522
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.935
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.436
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.056
And Tor is ready 18.155
Then the Upgrader considers the system as up-to-date 0.433
# 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.342
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.003
After features/support/hooks.rb:320 0.789
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
35.736
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 9.920
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 1.932
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 15.291
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.076
After features/support/hooks.rb:320 0.745
After features/support/hooks.rb:100 0.000