Project Number Date
test_Tails_ISO_stable 5105 20 Sep 2024, 08:24

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:7.684 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:13.736
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.522
When I start Tails from USB drive "old" with network unplugged 1:39.467
Then the boot device has safe access rights 3.491
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.507
After features/support/hooks.rb:100 0.028
Tags: @product
2:6.267
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:23.716
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 31.256
And I take note of which tps features are available 1.690
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 8.283
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.018
Tags: @product
2:53.190
Before features/support/hooks.rb:269 0.004
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.254
Then Tails is running from USB drive "old" 0.409
And all tps features are active 1.990
When I write some files expected to persist 1.828
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.300
And all persistence configuration files have safe access rights 0.542
And all persistent directories from the old Tails version have safe access rights 2.534
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.378
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.236
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.451
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.119
And I log in to a new session 20.366
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.799
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.763
Then the running Tails is installed on USB drive "to_upgrade" 18.407
And I unplug USB drive "to_upgrade" 0.305
And I unplug USB drive "__internal" 0.250
After features/support/hooks.rb:326 3.251
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.998
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.182
Then all tps features from the old Tails version are active 1.720
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.312
And the expected persistent files created with the old Tails version are present in the filesystem 1.772
And all persistent directories from the old Tails version have safe access rights 2.477
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.426
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 15.994
And no SquashFS delta is installed 0.170
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.085
And Tor is ready 19.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.733
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.728
Given I shutdown Tails and wait for the computer to power off 10.581
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.213
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.110
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.384
When the network is plugged 0.086
And Tor is ready 18.498
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.026
Given I shutdown Tails and wait for the computer to power off 4.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.169
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.060
And Tor is ready 19.563
Then the Upgrader considers the system as up-to-date 0.337
# 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 13.725
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.039
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.614
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 10.394
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
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 0.786
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 16.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.377
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.000