Project Number Date
test_Tails_ISO_15268-explain-admin-password 1 16 Jul 2025, 03:15

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 39:26.010 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
4:0.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.074
And I write an old version of the Tails USB image to disk "old" 1:1.340
When I start Tails from USB drive "old" with network unplugged 2:42.037
Then the boot device has safe access rights 14.750
And Tails is running from USB drive "old" 0.587
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:330 3.814
After features/support/hooks.rb:100 0.035
Tags: @product
4:35.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login 2:57.478
Then Tails is running from USB drive "old" 1.293
And I create a persistent partition 1:5.939
And I take note of which tps features are available 8.704
Then a Tails persistence partition exists on USB drive "old" 1.416
And I shutdown Tails and wait for the computer to power off 20.160
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.015
Tags: @product
6:20.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:40.965
Then Tails is running from USB drive "old" 1.201
And all tps features are active 2.938
When I write some files expected to persist 13.183
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.396
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 3.191
And I take note of which tps features are available 0.613
And I shutdown Tails and wait for the computer to power off 15.643
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 1:1.310
After features/support/hooks.rb:330 0.191
After features/support/hooks.rb:100 0.012
Tags: @product
4:58.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 49.153
And I log in to a new session 35.654
And I clone USB drive "old" to a new USB drive "to_upgrade" 13.488
And I plug USB drive "to_upgrade" 2.949
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:20.079
Then the running Tails is installed on USB drive "to_upgrade" 56.157
And I unplug USB drive "to_upgrade" 0.518
And I unplug USB drive "__internal" 0.483
After features/support/hooks.rb:330 4.244
After features/support/hooks.rb:100 0.000
Tags: @product
4:35.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.400
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:5.012
Then all tps features from the old Tails version are active 10.149
And Tails is running from USB drive "to_upgrade" 0.419
And the boot device has safe access rights 4.595
And the expected persistent files created with the old Tails version are present in the filesystem 1.914
And all persistent directories from the old Tails version have safe access rights 13.287
After features/support/hooks.rb:330 1.535
After features/support/hooks.rb:100 0.007
13:19.434
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 29.038
And no SquashFS delta is installed 2.586
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.053
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.886
And the file system changes introduced in version 6.2~testoverlayfs are not present 2.576
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.891
When the network is plugged 0.212
And Tor is ready 40.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 18.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.742
Given I shutdown Tails and wait for the computer to power off 18.590
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:2.428
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 3.561
And the file system changes introduced in version 6.2~testoverlayfs are present 0.693
And only the 6.2~testoverlayfs SquashFS delta is installed 0.108
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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 1.293
When the network is plugged 1.023
And Tor is ready 58.477
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.726
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 21.326
Given I shutdown Tails and wait for the computer to power off 6.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:39.743
Then Tails is running version 6.3~testoverlayfs 0.088
And all tps features are active 12.125
And the file system changes introduced in version 6.3~testoverlayfs are present 0.768
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.083
And Tor is ready 40.844
Then the Upgrader considers the system as up-to-date 0.504
# 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 36.545
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.715
After features/support/hooks.rb:330 0.874
After features/support/hooks.rb:100 0.014
1:36.111
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 32.446
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.092
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.687
And the signing key used by the Upgrader is outdated 0.325
But a current signing key is available on our website 0.000
When the network is plugged 0.112
And Tor is ready 41.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 18.928
After features/support/hooks.rb:330 1.555
After features/support/hooks.rb:100 0.000