Project Number Date
test_Tails_ISO_stable 5302 28 Nov 2024, 17:53

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:55.312 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.588
Before features/support/hooks.rb:269 0.005
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 33.880
When I start Tails from USB drive "old" with network unplugged 1:30.398
Then the boot device has safe access rights 3.019
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.783
After features/support/hooks.rb:100 0.011
Tags: @product
2:20.130
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:34.443
Then Tails is running from USB drive "old" 0.420
And I create a persistent partition 33.043
And I take note of which tps features are available 2.845
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.313
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.518
Before features/support/hooks.rb:269 0.006
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.398
Then Tails is running from USB drive "old" 0.411
And all tps features are active 1.888
When I write some files expected to persist 2.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.289
And all persistence configuration files have safe access rights 0.611
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 4.588
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.030
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.096
Before features/support/hooks.rb:269 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 11.200
And I log in to a new session 19.976
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.023
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.485
Then the running Tails is installed on USB drive "to_upgrade" 23.492
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 2.964
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.448
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.903
Then all tps features from the old Tails version are active 1.821
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.246
And the expected persistent files created with the old Tails version are present in the filesystem 1.513
And all persistent directories from the old Tails version have safe access rights 2.437
After features/support/hooks.rb:326 0.699
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:57.253
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 13.152
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.067
And Tor is ready 48.855
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.622
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.009
Given I shutdown Tails and wait for the computer to power off 10.751
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.860
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.148
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# 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.373
When the network is plugged 0.065
And Tor is ready 17.701
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.744
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.628
Given I shutdown Tails and wait for the computer to power off 4.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.682
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.155
And the file system changes introduced in version 6.3~testoverlayfs are present 0.666
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.391
When the network is plugged 0.077
And Tor is ready 18.622
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.290
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.067
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.275
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.727
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.410
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.837
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 18.732
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.420
After features/support/hooks.rb:326 1.232
After features/support/hooks.rb:100 0.000