Project Number Date
test_Tails_ISO_stable 4852 24 May 2024, 13:21

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:27.072 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
3:5.583
Before features/support/hooks.rb:259 0.007
Given a computer 0.251
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 1:22.096
When I start Tails from USB drive "old" with network unplugged 1:37.728
Then the boot device has safe access rights 3.371
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:305 7.425
After features/support/hooks.rb:89 0.008
Tags: @product
2:17.179
Before features/support/hooks.rb:259 0.006
Given a computer 0.355
And I start Tails from USB drive "old" with network unplugged and I login 1:27.176
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 38.191
And I take note of which tps features are available 1.586
Then a Tails persistence partition exists on USB drive "old" 0.832
And I shutdown Tails and wait for the computer to power off 8.655
After features/support/hooks.rb:305 0.161
After features/support/hooks.rb:89 0.008
Tags: @product
3:0.151
Before features/support/hooks.rb:259 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.668
Then Tails is running from USB drive "old" 0.471
And all tps features are active 2.231
When I write some files expected to persist 1.711
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.773
And I take note of which tps features are available 2.612
And I shutdown Tails and wait for the computer to power off 4.225
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.592
After features/support/hooks.rb:305 0.132
After features/support/hooks.rb:89 0.010
Tags: @product
2:30.727
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.930
And I log in to a new session 19.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.432
And I plug USB drive "to_upgrade" 2.540
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.501
Then the running Tails is installed on USB drive "to_upgrade" 22.560
And I unplug USB drive "to_upgrade" 0.385
And I unplug USB drive "__internal" 0.257
After features/support/hooks.rb:305 3.595
After features/support/hooks.rb:89 0.000
Tags: @product
2:19.408
Before features/support/hooks.rb:259 0.007
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.329
Then all tps features from the old Tails version are active 1.718
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.519
And the expected persistent files created with the old Tails version are present in the filesystem 1.679
And all persistent directories from the old Tails version have safe access rights 2.601
After features/support/hooks.rb:305 1.110
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:35.818
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.831
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.042
And Tor is ready 19.186
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.817
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.445
Given I shutdown Tails and wait for the computer to power off 8.848
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.025
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.467
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.352
When the network is plugged 0.045
And Tor is ready 19.217
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.402
Given I shutdown Tails and wait for the computer to power off 4.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.634
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.038
And Tor is ready 19.438
Then the Upgrader considers the system as up-to-date 0.333
# 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.304
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.032
After features/support/hooks.rb:305 0.910
After features/support/hooks.rb:89 0.015
Tags: @product @automatic_upgrade
38.202
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.536
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.466
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 20.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.897
After features/support/hooks.rb:305 0.726
After features/support/hooks.rb:89 0.000