Project Number Date
test_Tails_ISO_stable 5384 09 Jan 2025, 17:38

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:41.082 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:34.118
Before features/support/hooks.rb:269 0.004
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 41.174
When I start Tails from USB drive "old" with network unplugged 1:47.388
Then the boot device has safe access rights 3.214
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.346
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 8.308
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.386
Before features/support/hooks.rb:269 0.005
Given a computer 0.778
And I start Tails from USB drive "old" with network unplugged and I login 1:29.928
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 31.853
And I take note of which tps features are available 2.741
Then a Tails persistence partition exists on USB drive "old" 0.880
And I shutdown Tails and wait for the computer to power off 6.814
After features/support/hooks.rb:326 0.233
After features/support/hooks.rb:100 0.008
Tags: @product
3:7.641
Before features/support/hooks.rb:269 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.337
Then Tails is running from USB drive "old" 1.405
And all tps features are active 4.378
When I write some files expected to persist 2.145
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 3.529
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.498
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.933
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.726
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 12.068
And I log in to a new session 19.362
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.240
And I plug USB drive "to_upgrade" 2.440
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.090
Then the running Tails is installed on USB drive "to_upgrade" 24.076
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:326 2.250
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.741
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.635
Then all tps features from the old Tails version are active 1.803
And Tails is running from USB drive "to_upgrade" 0.531
And the boot device has safe access rights 3.324
And the expected persistent files created with the old Tails version are present in the filesystem 1.601
And all persistent directories from the old Tails version have safe access rights 2.642
After features/support/hooks.rb:326 0.852
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
7:6.751
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.027
And no SquashFS delta is installed 0.171
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
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.477
When the network is plugged 0.068
And Tor is ready 50.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.595
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.048
Given I shutdown Tails and wait for the computer to power off 11.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.006
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 5.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.395
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.410
When the network is plugged 0.326
And Tor is ready 18.458
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.519
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.324
Given I shutdown Tails and wait for the computer to power off 4.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.534
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 6.625
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.078
And Tor is ready 18.080
Then the Upgrader considers the system as up-to-date 0.323
# 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.085
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.999
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
38.717
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 10.244
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 20.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.284
After features/support/hooks.rb:326 1.034
After features/support/hooks.rb:100 0.000