Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 10 08 Oct 2024, 00:57

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:22.282 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:59.591
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.660
When I start Tails from USB drive "old" with network unplugged 1:24.849
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.534
After features/support/hooks.rb:100 0.024
Tags: @product
2:3.085
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:22.762
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 29.020
And I take note of which tps features are available 1.842
Then a Tails persistence partition exists on USB drive "old" 0.762
And I shutdown Tails and wait for the computer to power off 8.199
After features/support/hooks.rb:326 0.219
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.388
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.175
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.068
When I write some files expected to persist 1.799
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 2.335
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 4.245
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.224
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.157
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.188
And I log in to a new session 18.409
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.554
And I plug USB drive "to_upgrade" 2.392
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.996
Then the running Tails is installed on USB drive "to_upgrade" 22.206
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 1.773
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.418
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.372
Then all tps features from the old Tails version are active 1.574
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.022
And the expected persistent files created with the old Tails version are present in the filesystem 1.598
And all persistent directories from the old Tails version have safe access rights 2.365
After features/support/hooks.rb:326 0.781
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:16.684
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.114
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.464
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.070
And Tor is ready 17.746
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.486
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.808
Given I shutdown Tails and wait for the computer to power off 8.831
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.128
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.225
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.368
# 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.298
When the network is plugged 0.115
And Tor is ready 18.176
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.232
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.507
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.530
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.080
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.388
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.084
And Tor is ready 19.689
Then the Upgrader considers the system as up-to-date 0.312
# 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 13.511
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.089
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
34.956
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 9.870
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 1.194
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.295
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.180
After features/support/hooks.rb:326 0.920
After features/support/hooks.rb:100 0.000