Project Number Date
test_Tails_ISO_devel 3454 10 Jul 2024, 12:40

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:13.086 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:26.620
Before features/support/hooks.rb:269 0.005
Given a computer 0.244
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.027
When I start Tails from USB drive "old" with network unplugged 1:51.099
Then the boot device has safe access rights 3.129
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 3.509
After features/support/hooks.rb:100 0.028
Tags: @product
2:2.704
Before features/support/hooks.rb:269 0.008
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login 1:20.208
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 31.455
And I take note of which tps features are available 1.380
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.299
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.267
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.084
Then Tails is running from USB drive "old" 0.276
And all tps features are active 1.935
When I write some files expected to persist 1.673
# 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.411
And all persistent directories from the old Tails version have safe access rights 2.443
And I take note of which tps features are available 0.573
And I shutdown Tails and wait for the computer to power off 4.311
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.129
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.683
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.881
And I log in to a new session 21.322
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.336
And I plug USB drive "to_upgrade" 2.573
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.241
Then the running Tails is installed on USB drive "to_upgrade" 22.935
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.509
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.008
Before features/support/hooks.rb:269 0.007
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.916
Then all tps features from the old Tails version are active 1.597
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.042
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.306
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
6:46.163
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 11.679
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 0.096
And Tor is ready 24.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.478
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.715
Given I shutdown Tails and wait for the computer to power off 10.923
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.875
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.275
When the network is plugged 0.041
And Tor is ready 20.318
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.404
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.895
Given I shutdown Tails and wait for the computer to power off 4.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.365
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.266
And the file system changes introduced in version 6.3~testoverlayfs are present 0.670
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.037
And Tor is ready 17.655
Then the Upgrader considers the system as up-to-date 0.320
# 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.536
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.953
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.639
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.403
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.910
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 20.328
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.464
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.000