Project Number Date
test_Tails_ISO_stable 4997 05 Aug 2024, 12:24

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:29.440 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:25.621
Before features/support/hooks.rb:269 0.005
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.996
When I start Tails from USB drive "old" with network unplugged 1:51.115
Then the boot device has safe access rights 3.132
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.074
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.973
Before features/support/hooks.rb:269 0.006
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login 1:21.956
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 30.867
And I take note of which tps features are available 1.535
Then a Tails persistence partition exists on USB drive "old" 0.802
And I shutdown Tails and wait for the computer to power off 8.193
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.012
Tags: @product
2:53.625
Before features/support/hooks.rb:269 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.522
Then Tails is running from USB drive "old" 0.324
And all tps features are active 2.077
When I write some files expected to persist 1.814
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.309
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.131
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.083
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.011
Tags: @product
2:53.216
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 23.466
And I log in to a new session 21.028
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.746
And I plug USB drive "to_upgrade" 2.539
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.578
Then the running Tails is installed on USB drive "to_upgrade" 25.316
And I unplug USB drive "to_upgrade" 0.329
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 1.920
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.770
Before features/support/hooks.rb:269 0.006
Given a computer 0.375
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.593
Then all tps features from the old Tails version are active 3.101
And Tails is running from USB drive "to_upgrade" 0.482
And the boot device has safe access rights 3.878
And the expected persistent files created with the old Tails version are present in the filesystem 1.629
And all persistent directories from the old Tails version have safe access rights 2.708
After features/support/hooks.rb:326 0.922
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:56.255
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 18.920
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.738
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.451
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.479
And Tor is ready 21.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.187
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.039
Given I shutdown Tails and wait for the computer to power off 1:21.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.370
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.628
And the file system changes introduced in version 6.2~testoverlayfs are present 0.377
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.357
# 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.367
When the network is plugged 0.045
And Tor is ready 18.339
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.261
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.995
Given I shutdown Tails and wait for the computer to power off 4.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.597
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.412
And the file system changes introduced in version 6.3~testoverlayfs are present 0.588
And only the 6.3~testoverlayfs SquashFS delta is installed 0.133
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.059
And Tor is ready 21.385
Then the Upgrader considers the system as up-to-date 0.451
# 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 17.639
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.476
After features/support/hooks.rb:326 1.046
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
44.977
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 12.034
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.456
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 1.009
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 24.213
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.110
After features/support/hooks.rb:326 1.088
After features/support/hooks.rb:100 0.000