Project Number Date
test_Tails_ISO_stable 5095 12 Sep 2024, 08:45

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:47.138 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:21.257
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.782
When I start Tails from USB drive "old" with network unplugged 1:42.770
Then the boot device has safe access rights 3.346
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 10.333
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.239
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:22.771
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 33.227
And I take note of which tps features are available 1.800
Then a Tails persistence partition exists on USB drive "old" 0.897
And I shutdown Tails and wait for the computer to power off 8.917
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.012
Tags: @product
3:0.011
Before features/support/hooks.rb:269 0.007
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.537
Then Tails is running from USB drive "old" 0.434
And all tps features are active 2.341
When I write some files expected to persist 1.910
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.353
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 2.486
And I take note of which tps features are available 0.539
And I shutdown Tails and wait for the computer to power off 4.106
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.646
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.011
Tags: @product
2:40.277
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.415
And I log in to a new session 19.522
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.905
And I plug USB drive "to_upgrade" 2.524
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.335
Then the running Tails is installed on USB drive "to_upgrade" 26.087
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:326 2.034
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.125
Before features/support/hooks.rb:269 0.007
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.284
Then all tps features from the old Tails version are active 1.824
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 4.112
And the expected persistent files created with the old Tails version are present in the filesystem 1.758
And all persistent directories from the old Tails version have safe access rights 2.563
After features/support/hooks.rb:326 0.667
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:38.508
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.370
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.068
And Tor is ready 18.544
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.087
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.962
Given I shutdown Tails and wait for the computer to power off 8.669
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.451
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.368
And the file system changes introduced in version 6.2~testoverlayfs are present 0.400
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.291
When the network is plugged 0.076
And Tor is ready 17.573
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.028
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.934
Given I shutdown Tails and wait for the computer to power off 4.508
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.900
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.179
And the file system changes introduced in version 6.3~testoverlayfs are present 0.553
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.465
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.094
And Tor is ready 17.142
Then the Upgrader considers the system as up-to-date 0.366
# 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.051
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.086
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.718
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.938
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 1.420
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 19.452
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.417
After features/support/hooks.rb:326 2.038
After features/support/hooks.rb:100 0.000