Project Number Date
test_Tails_ISO_18215-update-chutney-force-all-tests 12 28 Mar 2025, 12:51

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 21:56.780 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:20.940
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.884
When I start Tails from USB drive "old" with network unplugged 1:44.483
Then the boot device has safe access rights 3.178
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 4.063
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:32.587
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 31.348
And I take note of which tps features are available 1.862
Then a Tails persistence partition exists on USB drive "old" 0.836
And I shutdown Tails and wait for the computer to power off 6.865
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.008
Tags: @product
3:8.308
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.352
Then Tails is running from USB drive "old" 0.498
And all tps features are active 2.403
When I write some files expected to persist 3.090
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 3.293
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.300
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.042
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.188
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.715
And I log in to a new session 21.391
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.650
And I plug USB drive "to_upgrade" 2.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.847
Then the running Tails is installed on USB drive "to_upgrade" 26.684
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 2.187
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.601
Then all tps features from the old Tails version are active 1.782
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.956
And the expected persistent files created with the old Tails version are present in the filesystem 1.448
And all persistent directories from the old Tails version have safe access rights 2.595
After features/support/hooks.rb:330 1.632
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:22.237
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.061
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.834
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.664
When the network is plugged 0.092
And Tor is ready 21.063
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.137
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.501
Given I shutdown Tails and wait for the computer to power off 9.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.113
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.494
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.144
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.468
When the network is plugged 0.067
And Tor is ready 20.634
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.306
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.551
Given I shutdown Tails and wait for the computer to power off 1:16.641
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.642
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.131
And the file system changes introduced in version 6.3~testoverlayfs are present 0.630
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.363
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.147
And Tor is ready 22.604
Then the Upgrader considers the system as up-to-date 0.358
# 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.856
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.142
After features/support/hooks.rb:330 0.762
After features/support/hooks.rb:100 0.068
Tags: @product @automatic_upgrade
39.007
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.409
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 19.405
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.390
After features/support/hooks.rb:330 0.739
After features/support/hooks.rb:100 0.000