Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 15 12 Oct 2024, 01:03

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:58.221 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:53.275
Before features/support/hooks.rb:269 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.109
When I start Tails from USB drive "old" with network unplugged 1:19.089
Then the boot device has safe access rights 2.854
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 7.340
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.658
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:27.170
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 32.259
And I take note of which tps features are available 1.374
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 6.566
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.519
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.327
Then Tails is running from USB drive "old" 1.612
And all tps features are active 2.039
When I write some files expected to persist 2.835
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.274
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 4.288
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.879
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.670
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.792
And I log in to a new session 18.166
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.455
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.983
Then the running Tails is installed on USB drive "to_upgrade" 16.486
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 6.808
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.543
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.837
Then all tps features from the old Tails version are active 1.590
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.810
And the expected persistent files created with the old Tails version are present in the filesystem 1.518
And all persistent directories from the old Tails version have safe access rights 2.291
After features/support/hooks.rb:326 0.913
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:56.962
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 12.414
And no SquashFS delta is installed 0.433
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.075
And Tor is ready 18.056
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.501
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.550
Given I shutdown Tails and wait for the computer to power off 10.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.019
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.007
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.288
When the network is plugged 0.063
And Tor is ready 20.059
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.217
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.166
Given I shutdown Tails and wait for the computer to power off 4.205
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.002
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.207
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.061
And Tor is ready 48.464
Then the Upgrader considers the system as up-to-date 0.317
# 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.695
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.819
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.591
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.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.008
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.753
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 18.527
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.379
After features/support/hooks.rb:326 0.916
After features/support/hooks.rb:100 0.000