Project Number Date
test_Tails_ISO_stable 5044 25 Aug 2024, 12: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 19:17.027 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:17.300
Before features/support/hooks.rb:269 0.007
Given a computer 0.279
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.089
And I write an old version of the Tails USB image to disk "old" 30.108
When I start Tails from USB drive "old" with network unplugged 1:41.743
Then the boot device has safe access rights 2.994
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:326 3.754
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.322
Before features/support/hooks.rb:269 0.005
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:22.686
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 30.485
And I take note of which tps features are available 1.364
Then a Tails persistence partition exists on USB drive "old" 0.896
And I shutdown Tails and wait for the computer to power off 8.277
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.060
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.774
Then Tails is running from USB drive "old" 0.346
And all tps features are active 2.187
When I write some files expected to persist 2.108
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.318
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.336
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 4.279
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.559
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.011
Tags: @product
2:23.965
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.850
And I log in to a new session 17.851
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.471
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.355
Then the running Tails is installed on USB drive "to_upgrade" 17.635
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 2.755
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.092
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.055
Then all tps features from the old Tails version are active 1.552
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.159
And the expected persistent files created with the old Tails version are present in the filesystem 2.093
And all persistent directories from the old Tails version have safe access rights 2.703
After features/support/hooks.rb:326 0.977
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:20.648
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 12.008
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.065
And Tor is ready 21.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.662
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.283
Given I shutdown Tails and wait for the computer to power off 8.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.578
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.153
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.296
When the network is plugged 0.088
And Tor is ready 20.503
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.573
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.565
Given I shutdown Tails and wait for the computer to power off 4.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.110
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.567
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.363
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.072
And Tor is ready 17.974
Then the Upgrader considers the system as up-to-date 0.395
# 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 13.841
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.007
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
58.638
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.015
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.798
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 46.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.000