Project Number Date
test_Tails_ISO_devel 3662 26 Jan 2025, 17:43

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 23:10.898 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:8.530
Before features/support/hooks.rb:269 0.002
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.524
When I start Tails from USB drive "old" with network unplugged 1:32.493
Then the boot device has safe access rights 3.208
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 9.916
After features/support/hooks.rb:100 0.007
Tags: @product
2:5.949
Before features/support/hooks.rb:269 0.003
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:23.121
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 31.879
And I take note of which tps features are available 1.396
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.190
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.006
Tags: @product
2:49.345
Before features/support/hooks.rb:269 0.002
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.860
Then Tails is running from USB drive "old" 1.403
And all tps features are active 2.128
When I write some files expected to persist 2.409
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.281
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 3.004
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.309
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.936
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.007
Tags: @product
2:34.665
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.511
And I log in to a new session 24.193
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.743
And I plug USB drive "to_upgrade" 2.380
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.285
Then the running Tails is installed on USB drive "to_upgrade" 18.156
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 2.579
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.442
Before features/support/hooks.rb:269 0.003
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.667
Then all tps features from the old Tails version are active 1.505
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.042
And the expected persistent files created with the old Tails version are present in the filesystem 1.284
And all persistent directories from the old Tails version have safe access rights 2.396
After features/support/hooks.rb:326 0.872
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
10:45.691
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.256
And no SquashFS delta is installed 0.489
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.109
And Tor is ready 22.454
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.133
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4:23.864
Given I shutdown Tails and wait for the computer to power off 6.745
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.618
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.359
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
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.323
# 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.368
When the network is plugged 0.068
And Tor is ready 17.602
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.465
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.326
Given I shutdown Tails and wait for the computer to power off 6.384
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.614
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.009
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.091
And Tor is ready 19.479
Then the Upgrader considers the system as up-to-date 0.322
# 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.850
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.083
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
37.273
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.597
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.917
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.283
And Tor is ready 20.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.243
After features/support/hooks.rb:326 1.441
After features/support/hooks.rb:100 0.000