Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 11 20 Nov 2024, 17:07

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:29.591 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:11.619
Before features/support/hooks.rb:269 0.005
Given a computer 0.268
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.968
When I start Tails from USB drive "old" with network unplugged 1:36.011
Then the boot device has safe access rights 3.147
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:326 3.578
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.779
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:23.033
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 30.529
And I take note of which tps features are available 1.577
Then a Tails persistence partition exists on USB drive "old" 0.738
And I shutdown Tails and wait for the computer to power off 8.350
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.012
Tags: @product
2:53.800
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.568
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.030
When I write some files expected to persist 1.936
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.372
And I take note of which tps features are available 0.532
And I shutdown Tails and wait for the computer to power off 4.322
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.818
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.420
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 25.784
And I log in to a new session 20.882
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.711
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.608
Then the running Tails is installed on USB drive "to_upgrade" 24.432
And I unplug USB drive "to_upgrade" 0.350
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.256
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.548
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.754
Then all tps features from the old Tails version are active 1.697
And Tails is running from USB drive "to_upgrade" 0.406
And the boot device has safe access rights 3.618
And the expected persistent files created with the old Tails version are present in the filesystem 1.463
And all persistent directories from the old Tails version have safe access rights 2.398
After features/support/hooks.rb:326 0.626
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
6:32.303
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.918
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.658
When the network is plugged 0.108
And Tor is ready 19.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.521
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.031
Given I shutdown Tails and wait for the computer to power off 10.713
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.119
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.326
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.296
When the network is plugged 0.096
And Tor is ready 19.444
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.094
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.603
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.020
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.149
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.371
When the network is plugged 0.077
And Tor is ready 16.941
Then the Upgrader considers the system as up-to-date 10.842
# 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.174
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.001
After features/support/hooks.rb:326 0.742
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.120
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.730
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 1.056
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.691
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.050
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.000