Project Number Date
test_Tails_ISO_stable 5125 29 Sep 2024, 12:19

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:38.572 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.600
Before features/support/hooks.rb:269 0.003
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 28.990
When I start Tails from USB drive "old" with network unplugged 1:27.387
Then the boot device has safe access rights 3.000
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.568
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.381
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:21.326
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 30.791
And I take note of which tps features are available 1.685
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.202
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:43.970
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:7.248
Then Tails is running from USB drive "old" 0.358
And all tps features are active 2.018
When I write some files expected to persist 1.640
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 3.044
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.113
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.757
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 10.398
And I log in to a new session 19.958
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.551
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.389
Then the running Tails is installed on USB drive "to_upgrade" 17.609
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.756
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.531
Before features/support/hooks.rb:269 0.005
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.949
Then all tps features from the old Tails version are active 1.698
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.227
And the expected persistent files created with the old Tails version are present in the filesystem 1.577
And all persistent directories from the old Tails version have safe access rights 2.492
After features/support/hooks.rb:326 0.594
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:37.591
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.885
And no SquashFS delta is installed 0.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.969
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.214
And Tor is ready 23.867
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.128
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.320
Given I shutdown Tails and wait for the computer to power off 8.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.053
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.343
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
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.306
# 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.321
When the network is plugged 0.080
And Tor is ready 20.097
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.924
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.071
Given I shutdown Tails and wait for the computer to power off 4.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.085
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.183
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.092
And Tor is ready 20.818
Then the Upgrader considers the system as up-to-date 0.311
# 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.147
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.054
After features/support/hooks.rb:326 0.751
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
33.739
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.016
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.757
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 16.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.242
After features/support/hooks.rb:326 0.908
After features/support/hooks.rb:100 0.000