Project Number Date
test_Tails_ISO_stable 5090 10 Sep 2024, 15:47

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.299 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:6.514
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.335
When I start Tails from USB drive "old" with network unplugged 1:28.484
Then the boot device has safe access rights 3.226
And Tails is running from USB drive "old" 0.410
And there is no persistence partition on USB drive "old" 0.113
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:326 8.759
After features/support/hooks.rb:100 0.012
Tags: @product
2:11.417
Before features/support/hooks.rb:269 0.008
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:27.628
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.123
And I take note of which tps features are available 1.924
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.379
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.146
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.323
Then Tails is running from USB drive "old" 0.367
And all tps features are active 1.928
When I write some files expected to persist 1.659
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 2.603
And I take note of which tps features are available 0.400
And I shutdown Tails and wait for the computer to power off 4.373
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.608
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.933
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 14.161
And I log in to a new session 21.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.939
And I plug USB drive "to_upgrade" 2.511
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.941
Then the running Tails is installed on USB drive "to_upgrade" 21.852
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 2.161
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.658
Before features/support/hooks.rb:269 0.007
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.990
Then all tps features from the old Tails version are active 2.202
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.116
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 2.394
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:21.473
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 13.018
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.135
And Tor is ready 18.784
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.753
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.882
Given I shutdown Tails and wait for the computer to power off 8.796
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.949
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.076
And Tor is ready 20.144
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.948
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.271
Given I shutdown Tails and wait for the computer to power off 4.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.442
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.964
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.082
And Tor is ready 18.580
Then the Upgrader considers the system as up-to-date 0.329
# 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.062
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.046
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
34.155
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 10.496
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.801
But a current signing key is available on our website 0.000
When the network is plugged 0.310
And Tor is ready 18.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.884
After features/support/hooks.rb:326 1.494
After features/support/hooks.rb:100 0.000