Project Number Date
test_Tails_ISO_stable 5103 19 Sep 2024, 12:26

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:41.282 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:11.550
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.758
When I start Tails from USB drive "old" with network unplugged 1:33.991
Then the boot device has safe access rights 3.388
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.136
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.519
After features/support/hooks.rb:100 0.012
Tags: @product
2:9.342
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:26.362
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 31.744
And I take note of which tps features are available 1.656
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 8.224
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.114
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.218
Then Tails is running from USB drive "old" 0.375
And all tps features are active 2.961
When I write some files expected to persist 1.829
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.292
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.706
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.327
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.293
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.492
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.460
And I log in to a new session 20.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.626
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.144
Then the running Tails is installed on USB drive "to_upgrade" 21.574
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 2.780
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.262
Before features/support/hooks.rb:269 0.005
Given a computer 0.268
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.057
Then all tps features from the old Tails version are active 1.786
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.248
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 2.944
After features/support/hooks.rb:326 0.624
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
6:35.850
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.950
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.064
And Tor is ready 20.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.522
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.640
Given I shutdown Tails and wait for the computer to power off 11.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.361
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.385
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.269
When the network is plugged 0.077
And Tor is ready 15.584
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.493
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.268
Given I shutdown Tails and wait for the computer to power off 4.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.342
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.955
And the file system changes introduced in version 6.3~testoverlayfs are present 0.565
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.066
And Tor is ready 18.823
Then the Upgrader considers the system as up-to-date 0.306
# 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 14.820
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:326 0.729
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
58.669
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 9.712
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.777
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 47.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.582
After features/support/hooks.rb:326 0.875
After features/support/hooks.rb:100 0.000