Project Number Date
test_Tails_ISO_20522-ocr-more 53 03 Feb 2025, 21:53

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:24.333 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:4.855
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.735
When I start Tails from USB drive "old" with network unplugged 1:28.523
Then the boot device has safe access rights 3.205
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.256
After features/support/hooks.rb:326 7.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.124
Before features/support/hooks.rb:269 0.008
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:39.412
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 32.455
And I take note of which tps features are available 1.495
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.381
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.962
Before features/support/hooks.rb:269 0.005
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.011
Then Tails is running from USB drive "old" 1.727
And all tps features are active 2.189
When I write some files expected to persist 3.467
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.884
And I take note of which tps features are available 0.622
And I shutdown Tails and wait for the computer to power off 4.406
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.727
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.760
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 24.285
And I log in to a new session 18.459
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.710
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.471
Then the running Tails is installed on USB drive "to_upgrade" 22.982
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:326 2.577
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.139
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.974
Then all tps features from the old Tails version are active 1.964
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 4.021
And the expected persistent files created with the old Tails version are present in the filesystem 1.723
And all persistent directories from the old Tails version have safe access rights 2.839
After features/support/hooks.rb:326 1.027
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:54.263
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.642
And no SquashFS delta is installed 0.405
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.085
And Tor is ready 23.558
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.669
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.544
Given I shutdown Tails and wait for the computer to power off 10.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.990
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.315
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.410
# 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.342
When the network is plugged 0.080
And Tor is ready 19.347
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.331
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.902
Given I shutdown Tails and wait for the computer to power off 4.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.080
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.424
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.425
When the network is plugged 0.071
And Tor is ready 20.261
Then the Upgrader considers the system as up-to-date 0.344
# 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 14.981
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.075
After features/support/hooks.rb:326 0.781
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.227
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 22.395
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.161
After features/support/hooks.rb:326 0.658
After features/support/hooks.rb:100 0.000