Project Number Date
test_Tails_ISO_devel 3523 28 Sep 2024, 12:20

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:2.832 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:57.954
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 28.039
When I start Tails from USB drive "old" with network unplugged 1:24.750
Then the boot device has safe access rights 2.915
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:326 7.023
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.134
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:22.889
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 31.228
And I take note of which tps features are available 1.548
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.189
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.566
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.894
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.038
When I write some files expected to persist 1.782
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.623
And I take note of which tps features are available 0.415
And I shutdown Tails and wait for the computer to power off 4.299
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.384
After features/support/hooks.rb:326 0.097
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.061
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 11.247
And I log in to a new session 19.334
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.520
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.280
Then the running Tails is installed on USB drive "to_upgrade" 16.845
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 3.406
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.818
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.659
Then all tps features from the old Tails version are active 1.507
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 3.339
And the expected persistent files created with the old Tails version are present in the filesystem 1.461
And all persistent directories from the old Tails version have safe access rights 2.356
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:37.901
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.037
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.069
And Tor is ready 21.246
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.106
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.499
Given I shutdown Tails and wait for the computer to power off 8.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.156
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.383
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.298
When the network is plugged 0.073
And Tor is ready 20.577
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.252
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.464
Given I shutdown Tails and wait for the computer to power off 4.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.909
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.080
And Tor is ready 17.301
Then the Upgrader considers the system as up-to-date 10.732
# 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 13.644
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.926
After features/support/hooks.rb:326 0.691
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
56.395
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 9.971
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.825
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 44.611
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.569
After features/support/hooks.rb:326 0.673
After features/support/hooks.rb:100 0.000