Project Number Date
test_Tails_ISO_20522-ocr-more 33 18 Jan 2025, 05:21

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 19:25.913 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:12.065
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.566
When I start Tails from USB drive "old" with network unplugged 1:36.163
Then the boot device has safe access rights 3.013
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 7.043
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.811
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:21.690
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 31.827
And I take note of which tps features are available 1.449
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 8.444
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.275
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.976
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.183
When I write some files expected to persist 1.750
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.736
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 4.301
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.667
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.699
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 25.670
And I log in to a new session 17.409
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.486
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.759
Then the running Tails is installed on USB drive "to_upgrade" 22.482
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 6.631
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.334
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.272
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.754
And the expected persistent files created with the old Tails version are present in the filesystem 1.530
And all persistent directories from the old Tails version have safe access rights 2.492
After features/support/hooks.rb:326 0.658
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
6:24.827
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.398
And no SquashFS delta is installed 0.557
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.092
And Tor is ready 21.266
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.742
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.487
Given I shutdown Tails and wait for the computer to power off 8.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.376
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.166
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.262
When the network is plugged 0.065
And Tor is ready 19.483
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.159
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.930
Given I shutdown Tails and wait for the computer to power off 4.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.020
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.095
And Tor is ready 19.073
Then the Upgrader considers the system as up-to-date 0.317
# 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.116
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.315
After features/support/hooks.rb:326 0.810
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.898
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.815
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.747
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 20.183
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.948
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.000