Project Number Date
test_Tails_ISO_devel 3591 18 Nov 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 19:58.847 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:12.348
Before features/support/hooks.rb:269 0.018
Given a computer 0.304
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 31.383
When I start Tails from USB drive "old" with network unplugged 1:35.025
Then the boot device has safe access rights 3.367
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.106
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 7.286
After features/support/hooks.rb:100 0.013
Tags: @product
2:9.824
Before features/support/hooks.rb:269 0.008
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login 1:26.947
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 31.339
And I take note of which tps features are available 1.861
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.280
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.015
Tags: @product
3:5.366
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.514
Then Tails is running from USB drive "old" 0.532
And all tps features are active 2.443
When I write some files expected to persist 2.048
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.910
And I take note of which tps features are available 0.698
And I shutdown Tails and wait for the computer to power off 4.476
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.870
After features/support/hooks.rb:326 0.099
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.091
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 13.456
And I log in to a new session 22.300
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.568
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.841
Then the running Tails is installed on USB drive "to_upgrade" 19.096
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 3.330
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.128
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.501
Then all tps features from the old Tails version are active 1.805
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.778
And the expected persistent files created with the old Tails version are present in the filesystem 1.762
And all persistent directories from the old Tails version have safe access rights 2.669
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:55.909
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.560
And no SquashFS delta is installed 0.283
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.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.504
When the network is plugged 0.071
And Tor is ready 22.932
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.042
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.390
Given I shutdown Tails and wait for the computer to power off 10.468
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.302
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.652
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.325
When the network is plugged 0.092
And Tor is ready 20.375
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.320
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.102
Given I shutdown Tails and wait for the computer to power off 6.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.403
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.111
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.151
# 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.518
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.487
When the network is plugged 0.072
And Tor is ready 21.362
Then the Upgrader considers the system as up-to-date 0.338
# 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.186
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.361
After features/support/hooks.rb:326 0.802
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
41.177
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.823
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.866
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 1.266
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 21.611
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.465
After features/support/hooks.rb:326 1.520
After features/support/hooks.rb:100 0.000