Project Number Date
test_Tails_ISO_stable 5285 22 Nov 2024, 12:27

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:9.140 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:9.310
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 34.559
When I start Tails from USB drive "old" with network unplugged 1:29.546
Then the boot device has safe access rights 2.974
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 3.581
After features/support/hooks.rb:100 0.059
Tags: @product
2:7.712
Before features/support/hooks.rb:269 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:23.191
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 32.658
And I take note of which tps features are available 1.991
Then a Tails persistence partition exists on USB drive "old" 0.854
And I shutdown Tails and wait for the computer to power off 8.491
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.542
Before features/support/hooks.rb:269 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.419
Then Tails is running from USB drive "old" 0.371
And all tps features are active 1.785
When I write some files expected to persist 1.981
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.447
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.275
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.044
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.089
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.427
And I log in to a new session 23.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.286
And I plug USB drive "to_upgrade" 2.644
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.698
Then the running Tails is installed on USB drive "to_upgrade" 25.150
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:326 2.477
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.851
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.055
Then all tps features from the old Tails version are active 1.660
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.557
And the expected persistent files created with the old Tails version are present in the filesystem 1.474
And all persistent directories from the old Tails version have safe access rights 2.581
After features/support/hooks.rb:326 0.690
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:29.079
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 12.568
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.062
And Tor is ready 21.804
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.176
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.560
Given I shutdown Tails and wait for the computer to power off 10.877
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.781
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.263
When the network is plugged 0.081
And Tor is ready 16.345
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.403
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.503
Given I shutdown Tails and wait for the computer to power off 4.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.090
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.100
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.071
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.393
When the network is plugged 0.120
And Tor is ready 17.914
Then the Upgrader considers the system as up-to-date 0.309
# 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.053
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.222
After features/support/hooks.rb:326 0.814
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.554
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.630
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.935
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 21.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.255
After features/support/hooks.rb:326 0.791
After features/support/hooks.rb:100 0.000