Project Number Date
test_Tails_ISO_stable 5013 09 Aug 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 19:12.964 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:3.711
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.896
When I start Tails from USB drive "old" with network unplugged 1:28.600
Then the boot device has safe access rights 2.936
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.556
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.574
Before features/support/hooks.rb:269 0.013
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:25.728
Then Tails is running from USB drive "old" 0.433
And I create a persistent partition 31.939
And I take note of which tps features are available 2.098
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 8.292
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.224
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.498
Then Tails is running from USB drive "old" 0.307
And all tps features are active 1.959
When I write some files expected to persist 1.813
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.810
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.314
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.289
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.143
Before features/support/hooks.rb:269 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 13.304
And I log in to a new session 18.426
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.585
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.865
Then the running Tails is installed on USB drive "to_upgrade" 21.119
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.173
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.537
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.140
Then all tps features from the old Tails version are active 1.584
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.211
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.684
After features/support/hooks.rb:326 0.912
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:40.385
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.937
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.077
And Tor is ready 20.860
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.273
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.356
Given I shutdown Tails and wait for the computer to power off 8.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.379
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.070
And Tor is ready 21.086
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.549
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.416
Given I shutdown Tails and wait for the computer to power off 4.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.486
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.081
And Tor is ready 18.200
Then the Upgrader considers the system as up-to-date 10.807
# 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.055
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.742
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.388
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.003
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.057
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 17.796
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.391
After features/support/hooks.rb:326 1.036
After features/support/hooks.rb:100 0.000