Project Number Date
test_Tails_ISO_20522-ocr-more 30 08 Jan 2025, 05:30

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 18:36.901 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
1:49.117
Before features/support/hooks.rb:269 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.705
When I start Tails from USB drive "old" with network unplugged 1:15.021
Then the boot device has safe access rights 3.105
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.576
After features/support/hooks.rb:100 0.025
Tags: @product
2:13.886
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:31.862
Then Tails is running from USB drive "old" 0.438
And I create a persistent partition 30.869
And I take note of which tps features are available 1.452
Then a Tails persistence partition exists on USB drive "old" 0.784
And I shutdown Tails and wait for the computer to power off 8.292
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.008
Tags: @product
3:6.863
Before features/support/hooks.rb:269 0.004
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.244
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.151
When I write some files expected to persist 1.832
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.539
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.216
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.007
Tags: @product
2:30.148
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.562
And I log in to a new session 21.485
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.378
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.982
Then the running Tails is installed on USB drive "to_upgrade" 20.775
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 3.568
After features/support/hooks.rb:100 0.000
Tags: @product
2:1.787
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.179
Then all tps features from the old Tails version are active 1.897
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.215
And the expected persistent files created with the old Tails version are present in the filesystem 1.307
And all persistent directories from the old Tails version have safe access rights 2.675
After features/support/hooks.rb:326 1.582
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:18.977
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 11.885
And no SquashFS delta is installed 0.482
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.585
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.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.600
When the network is plugged 0.484
And Tor is ready 20.997
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.946
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.772
Given I shutdown Tails and wait for the computer to power off 8.589
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.549
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.281
When the network is plugged 0.073
And Tor is ready 18.605
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.969
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.975
Given I shutdown Tails and wait for the computer to power off 4.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.042
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.529
And the file system changes introduced in version 6.3~testoverlayfs are present 0.565
And only the 6.3~testoverlayfs SquashFS delta is installed 0.111
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.335
When the network is plugged 0.073
And Tor is ready 17.884
Then the Upgrader considers the system as up-to-date 0.364
# 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.932
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.201
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
36.120
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 9.639
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.590
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.165
After features/support/hooks.rb:326 0.755
After features/support/hooks.rb:100 0.000