Project Number Date
test_Tails_ISO_devel 3777 10 Apr 2025, 21:04

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 21:37.142 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:40.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.277
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.183
And I write an old version of the Tails USB image to disk "old" 35.082
When I start Tails from USB drive "old" with network unplugged 1:59.033
Then the boot device has safe access rights 3.828
And Tails is running from USB drive "old" 0.432
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.437
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:330 3.881
After features/support/hooks.rb:100 0.022
Tags: @product
2:15.922
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:29.601
Then Tails is running from USB drive "old" 0.440
And I create a persistent partition 34.343
And I take note of which tps features are available 2.101
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.456
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.011
Tags: @product
3:36.108
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:54.149
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.262
When I write some files expected to persist 1.899
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.498
And all persistent directories from the old Tails version have safe access rights 3.067
And I take note of which tps features are available 0.539
And I shutdown Tails and wait for the computer to power off 6.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.612
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.012
Tags: @product
3:7.775
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 without a persistent partition and stopped at Tails Greeter's login screen 34.220
And I log in to a new session 20.594
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.732
And I plug USB drive "to_upgrade" 2.570
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.839
Then the running Tails is installed on USB drive "to_upgrade" 27.394
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 0.782
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.693
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.262
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.280
Then all tps features from the old Tails version are active 2.187
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.546
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.514
After features/support/hooks.rb:330 1.461
After features/support/hooks.rb:100 0.010
6:54.596
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 17.361
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.433
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.091
And Tor is ready 22.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.582
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.653
Given I shutdown Tails and wait for the computer to power off 10.879
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.886
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.411
# 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.468
When the network is plugged 0.087
And Tor is ready 19.118
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.136
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.903
Given I shutdown Tails and wait for the computer to power off 4.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.654
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.387
And the file system changes introduced in version 6.3~testoverlayfs are present 0.558
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.370
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.084
And Tor is ready 17.511
Then the Upgrader considers the system as up-to-date 0.295
# 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.561
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.469
After features/support/hooks.rb:330 0.828
After features/support/hooks.rb:100 0.033
37.305
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.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 19.683
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.557
After features/support/hooks.rb:330 1.033
After features/support/hooks.rb:100 0.000