Project Number Date
test_Tails_ISO_stable 4811 25 Apr 2024, 16:03

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 22:56.911 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:59.165
Before features/support/hooks.rb:259 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.121
When I start Tails from USB drive "old" with network unplugged 1:24.980
Then the boot device has safe access rights 2.853
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:305 3.511
After features/support/hooks.rb:89 0.009
Tags: @product
2:14.632
Before features/support/hooks.rb:259 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:30.262
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 35.350
And I take note of which tps features are available 1.385
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 6.301
After features/support/hooks.rb:305 0.152
After features/support/hooks.rb:89 0.009
Tags: @product
2:46.450
Before features/support/hooks.rb:259 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.620
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.237
When I write some files expected to persist 1.597
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.672
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.177
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.616
After features/support/hooks.rb:305 0.157
After features/support/hooks.rb:89 0.011
Tags: @product
2:26.456
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.178
And I log in to a new session 18.513
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.394
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.792
Then the running Tails is installed on USB drive "to_upgrade" 18.754
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:305 7.286
After features/support/hooks.rb:89 0.000
Tags: @product
2:23.571
Before features/support/hooks.rb:259 0.006
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.613
Then all tps features from the old Tails version are active 1.483
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 3.017
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 2.407
After features/support/hooks.rb:305 0.847
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
9:48.968
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.726
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.046
And Tor is ready 34.098
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.589
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 2:18.162
Given I shutdown Tails and wait for the computer to power off 8.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.025
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.067
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.378
# 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.251
When the network is plugged 0.057
And Tor is ready 1:3.393
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.578
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.727
Given I shutdown Tails and wait for the computer to power off 4.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.035
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.050
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.063
And Tor is ready 47.493
Then the Upgrader considers the system as up-to-date 0.334
# 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.450
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.888
After features/support/hooks.rb:305 0.690
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
1:17.666
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.513
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.468
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 1:6.608
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.609
After features/support/hooks.rb:305 0.739
After features/support/hooks.rb:89 0.000