Project Number Date
test_Tails_ISO_stable 5359 28 Dec 2024, 12:20

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 18:59.006 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:1.266
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.814
When I start Tails from USB drive "old" with network unplugged 1:24.936
Then the boot device has safe access rights 3.298
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 7.159
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.696
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:25.104
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 33.381
And I take note of which tps features are available 1.372
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.477
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.948
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.507
Then Tails is running from USB drive "old" 1.137
And all tps features are active 2.072
When I write some files expected to persist 1.648
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 3.175
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.368
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.817
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.007
Tags: @product
2:28.612
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.712
And I log in to a new session 18.545
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.757
And I plug USB drive "to_upgrade" 2.363
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.522
Then the running Tails is installed on USB drive "to_upgrade" 22.295
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 3.516
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.213
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.988
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.147
And the expected persistent files created with the old Tails version are present in the filesystem 1.593
And all persistent directories from the old Tails version have safe access rights 2.335
After features/support/hooks.rb:326 0.650
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
6:40.031
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.114
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.083
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.096
And Tor is ready 20.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.766
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.739
Given I shutdown Tails and wait for the computer to power off 11.045
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.156
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.079
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.281
# 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.245
When the network is plugged 0.068
And Tor is ready 18.979
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.699
Given I shutdown Tails and wait for the computer to power off 4.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.520
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.018
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.102
And Tor is ready 18.589
Then the Upgrader considers the system as up-to-date 10.817
# 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 14.541
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.952
After features/support/hooks.rb:326 0.760
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
36.236
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.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
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.117
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 18.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.354
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.000