Project Number Date
test_Tails_ISO_feature-arti 95 22 Jun 2025, 17:30

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 22:55.467 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:24.829
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.144
And I plug USB drive "old" 1.090
And I write an old version of the Tails USB image to disk "old" 30.599
When I start Tails from USB drive "old" with network unplugged 1:47.585
Then the boot device has safe access rights 4.045
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 3.552
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:40.529
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 36.967
And I take note of which tps features are available 2.198
Then a Tails persistence partition exists on USB drive "old" 0.742
And I shutdown Tails and wait for the computer to power off 9.368
After features/support/hooks.rb:330 0.228
After features/support/hooks.rb:100 0.015
Tags: @product
3:30.136
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:46.624
Then Tails is running from USB drive "old" 0.713
And all tps features are active 1.946
When I write some files expected to persist 3.542
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 3.822
And I take note of which tps features are available 0.570
And I shutdown Tails and wait for the computer to power off 4.686
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.315
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.668
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 without a persistent partition and stopped at Tails Greeter's login screen 12.650
And I log in to a new session 24.654
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.446
And I plug USB drive "to_upgrade" 2.572
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.034
Then the running Tails is installed on USB drive "to_upgrade" 29.907
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 2.575
After features/support/hooks.rb:100 0.000
Tags: @product
2:46.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.284
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:35.031
Then all tps features from the old Tails version are active 1.621
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.507
And the expected persistent files created with the old Tails version are present in the filesystem 1.779
And all persistent directories from the old Tails version have safe access rights 3.922
After features/support/hooks.rb:330 1.033
After features/support/hooks.rb:100 0.009
8:4.593
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 13.571
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.604
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.585
When the network is plugged 0.073
And Tor is ready 26.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.540
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.695
Given I shutdown Tails and wait for the computer to power off 11.526
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.639
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.453
And the file system changes introduced in version 6.2~testoverlayfs are present 0.558
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.417
# 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.700
When the network is plugged 0.264
And Tor is ready 21.408
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.752
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.901
Given I shutdown Tails and wait for the computer to power off 7.742
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.132
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.530
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.094
When the network is plugged 1.587
And Tor is ready 23.371
Then the Upgrader considers the system as up-to-date 0.327
# 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 19.606
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.594
After features/support/hooks.rb:330 0.874
After features/support/hooks.rb:100 0.036
41.397
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.020
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.217
And the signing key used by the Upgrader is outdated 0.574
But a current signing key is available on our website 0.000
When the network is plugged 1.129
And Tor is ready 20.518
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.473
After features/support/hooks.rb:330 1.376
After features/support/hooks.rb:100 0.000