Project Number Date
test_Tails_ISO_stable 5190 17 Oct 2024, 08:57

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:44.995 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:45.330
Before features/support/hooks.rb:269 0.004
Given a computer 0.244
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 1:7.344
When I start Tails from USB drive "old" with network unplugged 1:32.082
Then the boot device has safe access rights 3.361
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.392
And I unplug USB drive "old" 0.250
After features/support/hooks.rb:326 7.240
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.506
Before features/support/hooks.rb:269 0.006
Given a computer 0.510
And I start Tails from USB drive "old" with network unplugged and I login 1:23.621
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 32.960
And I take note of which tps features are available 1.802
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 8.409
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.334
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.532
Then Tails is running from USB drive "old" 0.411
And all tps features are active 2.394
When I write some files expected to persist 1.978
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.520
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.374
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.832
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.663
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.911
And I log in to a new session 19.388
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.768
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.085
Then the running Tails is installed on USB drive "to_upgrade" 18.604
And I unplug USB drive "to_upgrade" 0.276
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:326 3.196
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.643
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.749
Then all tps features from the old Tails version are active 1.807
And Tails is running from USB drive "to_upgrade" 0.429
And the boot device has safe access rights 3.570
And the expected persistent files created with the old Tails version are present in the filesystem 1.513
And all persistent directories from the old Tails version have safe access rights 2.377
After features/support/hooks.rb:326 0.927
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:23.637
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.032
And no SquashFS delta is installed 4.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.119
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.489
When the network is plugged 0.074
And Tor is ready 21.753
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.682
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.199
Given I shutdown Tails and wait for the computer to power off 8.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.953
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.251
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
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.338
# 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.064
And Tor is ready 17.773
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.255
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.751
Given I shutdown Tails and wait for the computer to power off 6.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.727
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.473
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.423
When the network is plugged 0.088
And Tor is ready 19.579
Then the Upgrader considers the system as up-to-date 0.326
# 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.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.141
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.880
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.537
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.595
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.779
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 20.209
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.603
After features/support/hooks.rb:326 1.311
After features/support/hooks.rb:100 0.000