Project Number Date
test_Tails_ISO_fix-homepage-image 4 09 Jul 2025, 07:40

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:11.920 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
1:59.227
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.223
When I start Tails from USB drive "old" with network unplugged 1:23.953
Then the boot device has safe access rights 3.657
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.239
After features/support/hooks.rb:330 3.682
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.306
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:27.818
Then Tails is running from USB drive "old" 0.419
And I create a persistent partition 30.395
And I take note of which tps features are available 2.243
Then a Tails persistence partition exists on USB drive "old" 0.679
And I shutdown Tails and wait for the computer to power off 8.530
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.011
Tags: @product
3:9.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.374
Then Tails is running from USB drive "old" 0.408
And all tps features are active 2.511
When I write some files expected to persist 2.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.283
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.846
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 4.199
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.622
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.010
Tags: @product
2:42.451
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 10.355
And I log in to a new session 19.218
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.132
And I plug USB drive "to_upgrade" 2.529
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.893
Then the running Tails is installed on USB drive "to_upgrade" 25.857
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 2.352
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.688
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.551
Then all tps features from the old Tails version are active 1.780
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.907
And the expected persistent files created with the old Tails version are present in the filesystem 1.880
And all persistent directories from the old Tails version have safe access rights 3.024
After features/support/hooks.rb:330 1.356
After features/support/hooks.rb:100 0.010
7:2.335
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 11.403
And no SquashFS delta is installed 0.316
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.601
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.149
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.595
When the network is plugged 0.080
And Tor is ready 24.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.141
Given I shutdown Tails and wait for the computer to power off 6.815
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.644
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.864
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.415
# 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.381
When the network is plugged 0.105
And Tor is ready 22.282
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.471
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.557
Given I shutdown Tails and wait for the computer to power off 6.724
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.259
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.260
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.350
When the network is plugged 0.069
And Tor is ready 22.248
Then the Upgrader considers the system as up-to-date 0.324
# 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 17.418
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.803
After features/support/hooks.rb:330 1.942
After features/support/hooks.rb:100 0.021
40.766
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 with a persistent partition enabled and logged in 10.754
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.584
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.133
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 21.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.920
After features/support/hooks.rb:330 1.956
After features/support/hooks.rb:100 0.000