Project Number Date
test_Tails_ISO_stable 4780 09 Apr 2024, 13:01

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 16:36.941 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:33.267
Before features/support/hooks.rb:259 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 19.735
When I start Tails from USB drive "old" with network unplugged 1:8.079
Then the boot device has safe access rights 3.112
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.232
After features/support/hooks.rb:305 3.546
After features/support/hooks.rb:89 0.036
Tags: @product
2:0.275
Before features/support/hooks.rb:259 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:20.105
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 30.975
And I take note of which tps features are available 1.361
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 6.569
After features/support/hooks.rb:305 0.169
After features/support/hooks.rb:89 0.009
Tags: @product
2:27.330
Before features/support/hooks.rb:259 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.394
Then Tails is running from USB drive "old" 0.365
And all tps features are active 1.826
When I write some files expected to persist 1.726
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.560
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.345
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.800
After features/support/hooks.rb:305 0.133
After features/support/hooks.rb:89 0.008
Tags: @product
2:18.796
Before features/support/hooks.rb:259 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 11.129
And I log in to a new session 14.752
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.216
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.518
Then the running Tails is installed on USB drive "to_upgrade" 13.324
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:305 3.575
After features/support/hooks.rb:89 0.000
Tags: @product
1:57.629
Before features/support/hooks.rb:259 0.005
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.628
Then all tps features from the old Tails version are active 1.509
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.050
And the expected persistent files created with the old Tails version are present in the filesystem 1.385
And all persistent directories from the old Tails version have safe access rights 2.552
After features/support/hooks.rb:305 0.607
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
5:47.959
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.380
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.054
And Tor is ready 15.009
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.005
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.584
Given I shutdown Tails and wait for the computer to power off 6.707
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.029
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.073
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.267
When the network is plugged 0.036
And Tor is ready 19.327
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.687
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.202
Given I shutdown Tails and wait for the computer to power off 4.436
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.918
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.892
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.274
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.039
And Tor is ready 19.141
Then the Upgrader considers the system as up-to-date 0.263
# 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.159
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.809
After features/support/hooks.rb:305 0.706
After features/support/hooks.rb:89 0.017
Tags: @product @automatic_upgrade
31.682
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.832
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.679
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 14.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.431
After features/support/hooks.rb:305 0.733
After features/support/hooks.rb:89 0.000