Project Number Date
test_Tails_ISO_devel 3539 09 Oct 2024, 19:05

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:24.792 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:3.087
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.832
When I start Tails from USB drive "old" with network unplugged 1:25.587
Then the boot device has safe access rights 3.246
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.382
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 7.077
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.553
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:24.487
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 33.178
And I take note of which tps features are available 1.691
Then a Tails persistence partition exists on USB drive "old" 0.871
And I shutdown Tails and wait for the computer to power off 8.783
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.604
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:15.900
Then Tails is running from USB drive "old" 0.371
And all tps features are active 1.946
When I write some files expected to persist 1.911
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.356
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.523
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.479
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.436
And I log in to a new session 20.526
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.673
And I plug USB drive "to_upgrade" 2.556
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.750
Then the running Tails is installed on USB drive "to_upgrade" 20.147
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.092
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.338
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.280
Then all tps features from the old Tails version are active 1.785
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.660
And the expected persistent files created with the old Tails version are present in the filesystem 1.543
And all persistent directories from the old Tails version have safe access rights 2.460
After features/support/hooks.rb:326 0.655
After features/support/hooks.rb:100 0.063
Tags: @product @automatic_upgrade
6:58.117
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 12.723
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.530
When the network is plugged 0.111
And Tor is ready 49.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.606
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.267
Given I shutdown Tails and wait for the computer to power off 9.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.150
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.223
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.115
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.386
When the network is plugged 0.145
And Tor is ready 20.045
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.136
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.639
Given I shutdown Tails and wait for the computer to power off 4.597
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.472
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.439
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.071
And Tor is ready 20.504
Then the Upgrader considers the system as up-to-date 0.316
# 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.815
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.132
After features/support/hooks.rb:326 0.731
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.611
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 10.674
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.068
And the signing key used by the Upgrader is outdated 0.808
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.659
After features/support/hooks.rb:326 1.470
After features/support/hooks.rb:100 0.000