Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 3 11 Nov 2024, 16:58

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:15.118 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:5.242
Before features/support/hooks.rb:269 0.003
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 28.931
When I start Tails from USB drive "old" with network unplugged 1:30.769
Then the boot device has safe access rights 3.129
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:326 3.884
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.764
Before features/support/hooks.rb:269 0.004
Given a computer 0.847
And I start Tails from USB drive "old" with network unplugged and I login 1:23.926
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 31.670
And I take note of which tps features are available 1.778
Then a Tails persistence partition exists on USB drive "old" 0.838
And I shutdown Tails and wait for the computer to power off 8.357
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.679
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.912
Then Tails is running from USB drive "old" 0.307
And all tps features are active 2.035
When I write some files expected to persist 2.043
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.346
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.505
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.281
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.965
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.404
And I log in to a new session 17.607
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.401
And I plug USB drive "to_upgrade" 2.540
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.133
Then the running Tails is installed on USB drive "to_upgrade" 20.487
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:326 0.974
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.279
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.357
Then all tps features from the old Tails version are active 1.564
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.044
And the expected persistent files created with the old Tails version are present in the filesystem 1.487
And all persistent directories from the old Tails version have safe access rights 2.296
After features/support/hooks.rb:326 0.994
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:45.524
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.433
And no SquashFS delta is installed 0.379
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.060
And Tor is ready 50.804
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.565
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.400
Given I shutdown Tails and wait for the computer to power off 10.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.517
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.041
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.350
When the network is plugged 0.071
And Tor is ready 18.274
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.109
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.164
Given I shutdown Tails and wait for the computer to power off 4.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.529
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.048
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.369
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.063
And Tor is ready 20.024
Then the Upgrader considers the system as up-to-date 0.329
# 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.612
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.010
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.662
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 11.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.939
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.142
And Tor is ready 22.387
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.246
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.000