Project Number Date
test_Tails_ISO_stable 4943 15 Jul 2024, 14:17

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:26.186 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:58.514
Before features/support/hooks.rb:269 0.005
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.073
And I write an old version of the Tails USB image to disk "old" 47.236
When I start Tails from USB drive "old" with network unplugged 2:5.828
Then the boot device has safe access rights 3.086
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 3.738
After features/support/hooks.rb:100 0.010
Tags: @product
2:20.642
Before features/support/hooks.rb:269 0.007
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:21.007
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 43.064
And I take note of which tps features are available 6.520
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.673
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.398
Before features/support/hooks.rb:269 0.005
Given a computer 1.131
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.163
Then Tails is running from USB drive "old" 0.485
And all tps features are active 2.257
When I write some files expected to persist 1.719
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.663
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.545
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.290
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.761
And I log in to a new session 20.825
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.471
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.579
Then the running Tails is installed on USB drive "to_upgrade" 23.765
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:326 1.160
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.452
Before features/support/hooks.rb:269 0.021
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.753
Then all tps features from the old Tails version are active 1.799
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 3.236
And the expected persistent files created with the old Tails version are present in the filesystem 1.659
And all persistent directories from the old Tails version have safe access rights 2.418
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:28.918
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.620
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.039
And Tor is ready 18.546
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.709
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.189
Given I shutdown Tails and wait for the computer to power off 1:15.938
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.262
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.374
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.271
When the network is plugged 0.070
And Tor is ready 19.323
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.036
Given I shutdown Tails and wait for the computer to power off 4.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.348
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.214
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.369
When the network is plugged 0.049
And Tor is ready 17.283
Then the Upgrader considers the system as up-to-date 10.861
# 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.703
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.966
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.968
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.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
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.878
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 17.468
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.001
After features/support/hooks.rb:326 1.038
After features/support/hooks.rb:100 0.000