Project Number Date
test_Tails_ISO_stable 5053 28 Aug 2024, 08:50

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:26.952 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:15.808
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.831
When I start Tails from USB drive "old" with network unplugged 1:37.311
Then the boot device has safe access rights 3.229
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.160
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 3.789
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.558
Before features/support/hooks.rb:269 0.005
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:29.795
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 29.037
And I take note of which tps features are available 1.886
Then a Tails persistence partition exists on USB drive "old" 0.906
And I shutdown Tails and wait for the computer to power off 8.329
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.009
Tags: @product
3:16.272
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.373
Then Tails is running from USB drive "old" 0.341
And all tps features are active 2.232
When I write some files expected to persist 1.895
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.592
And all persistent directories from the old Tails version have safe access rights 3.047
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.719
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.110
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.248
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 12.906
And I log in to a new session 19.869
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.780
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.972
Then the running Tails is installed on USB drive "to_upgrade" 22.823
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:326 4.913
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.323
Before features/support/hooks.rb:269 0.007
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.296
Then all tps features from the old Tails version are active 1.749
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.632
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.597
After features/support/hooks.rb:326 0.926
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:8.132
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.340
And no SquashFS delta is installed 0.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.503
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.163
And Tor is ready 49.899
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.660
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.687
Given I shutdown Tails and wait for the computer to power off 8.774
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.428
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.276
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.366
When the network is plugged 0.069
And Tor is ready 17.117
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.434
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.028
Given I shutdown Tails and wait for the computer to power off 4.801
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.258
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.243
And the file system changes introduced in version 6.3~testoverlayfs are present 0.587
And only the 6.3~testoverlayfs SquashFS delta is installed 0.107
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.338
When the network is plugged 0.070
And Tor is ready 19.419
Then the Upgrader considers the system as up-to-date 0.336
# 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 15.325
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.808
After features/support/hooks.rb:326 0.710
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
39.608
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.383
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.833
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 20.405
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.400
After features/support/hooks.rb:326 0.772
After features/support/hooks.rb:100 0.000