Project Number Date
test_Tails_ISO_devel 3488 21 Aug 2024, 12:26

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:10.374 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:52.835
Before features/support/hooks.rb:269 0.005
Given a computer 0.252
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 28.676
When I start Tails from USB drive "old" with network unplugged 1:18.803
Then the boot device has safe access rights 3.035
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:326 6.818
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.426
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:27.787
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 31.500
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 8.433
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.011
Tags: @product
2:46.770
Before features/support/hooks.rb:269 0.008
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.342
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.982
When I write some files expected to persist 1.753
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.396
And I take note of which tps features are available 0.595
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.222
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.100
Before features/support/hooks.rb:269 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 28.155
And I log in to a new session 18.503
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.573
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.655
Then the running Tails is installed on USB drive "to_upgrade" 16.427
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 3.523
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.491
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.370
Then all tps features from the old Tails version are active 1.535
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.283
And the expected persistent files created with the old Tails version are present in the filesystem 1.291
And all persistent directories from the old Tails version have safe access rights 2.497
After features/support/hooks.rb:326 0.651
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:51.241
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 14.403
And no SquashFS delta is installed 1.242
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.499
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.844
When the network is plugged 0.225
And Tor is ready 18.522
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.588
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.156
Given I shutdown Tails and wait for the computer to power off 10.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.330
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.266
When the network is plugged 0.062
And Tor is ready 18.457
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.373
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.710
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.601
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.308
When the network is plugged 0.075
And Tor is ready 48.616
Then the Upgrader considers the system as up-to-date 0.305
# 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.516
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.091
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
33.508
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 9.878
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
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.815
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 15.946
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.428
After features/support/hooks.rb:326 1.357
After features/support/hooks.rb:100 0.000