Project Number Date
test_Tails_ISO_18215-update-chutney-force-all-tests 31 12 Apr 2025, 12:42

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 20:2.709 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:15.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.950
When I start Tails from USB drive "old" with network unplugged 1:37.015
Then the boot device has safe access rights 3.444
And Tails is running from USB drive "old" 0.402
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 7.060
After features/support/hooks.rb:100 0.011
Tags: @product
2:17.102
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:32.178
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 33.137
And I take note of which tps features are available 1.708
Then a Tails persistence partition exists on USB drive "old" 0.762
And I shutdown Tails and wait for the computer to power off 8.811
After features/support/hooks.rb:330 0.195
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.068
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.441
Then Tails is running from USB drive "old" 0.615
And all tps features are active 1.991
When I write some files expected to persist 1.776
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.676
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 6.770
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.467
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.417
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.328
And I log in to a new session 21.971
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.071
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.106
Then the running Tails is installed on USB drive "to_upgrade" 26.976
And I unplug USB drive "to_upgrade" 0.258
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 5.924
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.710
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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:11.384
Then all tps features from the old Tails version are active 1.889
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.642
And the expected persistent files created with the old Tails version are present in the filesystem 1.540
And all persistent directories from the old Tails version have safe access rights 2.678
After features/support/hooks.rb:330 1.060
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:52.214
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.546
And no SquashFS delta is installed 0.383
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.479
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.079
And Tor is ready 23.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.642
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.753
Given I shutdown Tails and wait for the computer to power off 8.911
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.616
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.485
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.368
# 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.302
When the network is plugged 0.080
And Tor is ready 23.922
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.126
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.985
Given I shutdown Tails and wait for the computer to power off 6.900
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.245
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.029
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.068
And Tor is ready 20.018
Then the Upgrader considers the system as up-to-date 0.300
# 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 16.209
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.848
After features/support/hooks.rb:330 0.707
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
40.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.963
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
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 0.112
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 21.166
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.520
After features/support/hooks.rb:330 0.687
After features/support/hooks.rb:100 0.000