Project Number Date
test_Tails_ISO_stable 5116 25 Sep 2024, 08:52

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:1.134 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:27.204
Before features/support/hooks.rb:269 0.007
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.045
When I start Tails from USB drive "old" with network unplugged 1:50.429
Then the boot device has safe access rights 3.327
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.379
And I unplug USB drive "old" 0.252
After features/support/hooks.rb:326 7.284
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.233
Before features/support/hooks.rb:269 0.007
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:31.007
Then Tails is running from USB drive "old" 0.534
And I create a persistent partition 34.581
And I take note of which tps features are available 2.063
Then a Tails persistence partition exists on USB drive "old" 0.910
And I shutdown Tails and wait for the computer to power off 8.918
After features/support/hooks.rb:326 0.212
After features/support/hooks.rb:100 0.008
Tags: @product
3:5.657
Before features/support/hooks.rb:269 0.004
Given a computer 0.382
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.543
Then Tails is running from USB drive "old" 1.282
And all tps features are active 2.453
When I write some files expected to persist 2.739
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 3.375
And I take note of which tps features are available 0.825
And I shutdown Tails and wait for the computer to power off 4.393
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.037
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.003
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 27.234
And I log in to a new session 20.739
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.980
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.714
Then the running Tails is installed on USB drive "to_upgrade" 20.444
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.540
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.358
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.155
Then all tps features from the old Tails version are active 1.813
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.503
And the expected persistent files created with the old Tails version are present in the filesystem 2.812
And all persistent directories from the old Tails version have safe access rights 2.519
After features/support/hooks.rb:326 0.864
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:11.255
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 17.253
And no SquashFS delta is installed 0.385
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.538
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.182
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.385
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.491
When the network is plugged 0.074
And Tor is ready 26.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.968
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.477
Given I shutdown Tails and wait for the computer to power off 11.119
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.962
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.503
And the file system changes introduced in version 6.2~testoverlayfs are present 0.402
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.283
When the network is plugged 0.081
And Tor is ready 17.458
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.244
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.322
Given I shutdown Tails and wait for the computer to power off 4.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.419
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.310
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.359
When the network is plugged 0.082
And Tor is ready 47.631
Then the Upgrader considers the system as up-to-date 0.338
# 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.505
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.076
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.087
Tags: @product @automatic_upgrade
43.421
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.707
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.480
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 1.414
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 21.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.957
After features/support/hooks.rb:326 2.824
After features/support/hooks.rb:100 0.000