Project Number Date
test_Tails_ISO_devel 3633 05 Jan 2025, 12:23

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:50.688 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
1:58.452
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.348
When I start Tails from USB drive "old" with network unplugged 1:24.614
Then the boot device has safe access rights 3.168
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 6.968
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.284
Before features/support/hooks.rb:269 0.006
Given a computer 0.315
And I start Tails from USB drive "old" with network unplugged and I login 1:21.449
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 30.466
And I take note of which tps features are available 1.486
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.427
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.477
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.126
Then Tails is running from USB drive "old" 0.326
And all tps features are active 2.043
When I write some files expected to persist 1.586
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.766
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.146
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.253
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.897
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.332
And I log in to a new session 19.078
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.702
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.320
Then the running Tails is installed on USB drive "to_upgrade" 21.647
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 2.288
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.025
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.068
Then all tps features from the old Tails version are active 1.638
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.398
And the expected persistent files created with the old Tails version are present in the filesystem 1.640
And all persistent directories from the old Tails version have safe access rights 2.765
After features/support/hooks.rb:326 0.672
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:38.116
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 13.580
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
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.517
When the network is plugged 0.067
And Tor is ready 20.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.174
Given I shutdown Tails and wait for the computer to power off 10.562
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.824
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# 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.383
When the network is plugged 0.085
And Tor is ready 21.383
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.849
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.764
Given I shutdown Tails and wait for the computer to power off 4.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.963
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.043
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.070
# 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.392
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.072
And Tor is ready 19.453
Then the Upgrader considers the system as up-to-date 10.773
# 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.016
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.942
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.433
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.663
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.864
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 21.748
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.693
After features/support/hooks.rb:326 1.289
After features/support/hooks.rb:100 0.000