Project Number Date
test_Tails_ISO_stable 5200 20 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 20:59.468 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:16.357
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.494
When I start Tails from USB drive "old" with network unplugged 1:37.411
Then the boot device has safe access rights 3.117
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 3.522
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.425
Before features/support/hooks.rb:269 0.005
Given a computer 0.271
And I start Tails from USB drive "old" with network unplugged and I login 1:29.715
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 33.539
And I take note of which tps features are available 4.162
Then a Tails persistence partition exists on USB drive "old" 0.999
And I shutdown Tails and wait for the computer to power off 8.357
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.008
Tags: @product
3:2.999
Before features/support/hooks.rb:269 0.006
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.467
Then Tails is running from USB drive "old" 0.411
And all tps features are active 2.492
When I write some files expected to persist 1.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.648
And I take note of which tps features are available 0.632
And I shutdown Tails and wait for the computer to power off 4.540
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.181
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.991
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 11.288
And I log in to a new session 20.066
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.915
And I plug USB drive "to_upgrade" 2.472
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.621
Then the running Tails is installed on USB drive "to_upgrade" 25.185
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 3.606
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.583
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.500
Then all tps features from the old Tails version are active 1.959
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.238
And the expected persistent files created with the old Tails version are present in the filesystem 1.734
And all persistent directories from the old Tails version have safe access rights 2.552
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:46.622
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 37.600
And no SquashFS delta is installed 0.469
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.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.090
And Tor is ready 23.967
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.646
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.273
Given I shutdown Tails and wait for the computer to power off 8.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.347
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.041
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.367
# 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.355
When the network is plugged 0.075
And Tor is ready 47.639
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.872
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.614
Given I shutdown Tails and wait for the computer to power off 6.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.071
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.279
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.102
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.081
And Tor is ready 18.579
Then the Upgrader considers the system as up-to-date 0.350
# 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.280
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.039
After features/support/hooks.rb:326 0.833
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
40.489
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 10.490
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.602
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 1.013
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 20.314
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.872
After features/support/hooks.rb:326 0.997
After features/support/hooks.rb:100 0.000