Project Number Date
test_Tails_ISO_devel 3500 02 Sep 2024, 12:52

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:22.320 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:31.565
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 41.774
When I start Tails from USB drive "old" with network unplugged 1:44.338
Then the boot device has safe access rights 3.112
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.527
After features/support/hooks.rb:100 0.067
Tags: @product
2:9.810
Before features/support/hooks.rb:269 0.007
Given a computer 0.276
And I start Tails from USB drive "old" with network unplugged and I login 1:25.662
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 32.761
And I take note of which tps features are available 1.630
Then a Tails persistence partition exists on USB drive "old" 0.870
And I shutdown Tails and wait for the computer to power off 8.252
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.011
Tags: @product
3:1.050
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.952
Then Tails is running from USB drive "old" 0.391
And all tps features are active 2.507
When I write some files expected to persist 2.424
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.811
And I take note of which tps features are available 0.607
And I shutdown Tails and wait for the computer to power off 4.257
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.138
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.269
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.094
And I log in to a new session 21.125
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.754
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.493
Then the running Tails is installed on USB drive "to_upgrade" 22.913
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.643
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.936
Before features/support/hooks.rb:269 0.007
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.742
Then all tps features from the old Tails version are active 1.689
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.437
And the expected persistent files created with the old Tails version are present in the filesystem 1.629
And all persistent directories from the old Tails version have safe access rights 2.849
After features/support/hooks.rb:326 0.961
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:1.796
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.344
And no SquashFS delta is installed 0.395
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.543
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.142
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.067
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.484
And Tor is ready 18.367
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.467
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.286
Given I shutdown Tails and wait for the computer to power off 9.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.629
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.595
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.314
When the network is plugged 0.090
And Tor is ready 20.364
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.552
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.616
Given I shutdown Tails and wait for the computer to power off 4.702
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.060
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.460
And the file system changes introduced in version 6.3~testoverlayfs are present 0.543
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.285
When the network is plugged 0.068
And Tor is ready 20.412
Then the Upgrader considers the system as up-to-date 0.379
# 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.382
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.090
After features/support/hooks.rb:326 0.790
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.890
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 10.203
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 1.085
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 20.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.887
After features/support/hooks.rb:326 1.265
After features/support/hooks.rb:100 0.000