Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 26 23 Oct 2024, 00:41

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:42.651 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:54.913
Before features/support/hooks.rb:269 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.314
When I start Tails from USB drive "old" with network unplugged 1:20.607
Then the boot device has safe access rights 2.791
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.738
After features/support/hooks.rb:100 0.007
Tags: @product
2:1.683
Before features/support/hooks.rb:269 0.004
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:19.764
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 31.240
And I take note of which tps features are available 1.358
Then a Tails persistence partition exists on USB drive "old" 0.728
And I shutdown Tails and wait for the computer to power off 8.111
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.767
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.685
Then Tails is running from USB drive "old" 1.453
And all tps features are active 1.971
When I write some files expected to persist 2.539
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 3.321
And I take note of which tps features are available 0.393
And I shutdown Tails and wait for the computer to power off 4.640
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.966
After features/support/hooks.rb:326 0.090
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.227
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.705
And I log in to a new session 17.550
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.523
And I plug USB drive "to_upgrade" 2.365
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.845
Then the running Tails is installed on USB drive "to_upgrade" 19.846
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 2.194
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.065
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.356
Then all tps features from the old Tails version are active 1.531
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.014
And the expected persistent files created with the old Tails version are present in the filesystem 1.342
And all persistent directories from the old Tails version have safe access rights 2.333
After features/support/hooks.rb:326 0.880
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:12.783
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.079
And no SquashFS delta is installed 0.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.553
When the network is plugged 0.075
And Tor is ready 24.685
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.432
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.267
Given I shutdown Tails and wait for the computer to power off 8.368
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.755
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.059
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
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.297
# 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.253
When the network is plugged 0.082
And Tor is ready 16.561
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.730
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.356
Given I shutdown Tails and wait for the computer to power off 59.808
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.438
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.931
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.064
And Tor is ready 19.933
Then the Upgrader considers the system as up-to-date 0.319
# 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.373
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.871
After features/support/hooks.rb:326 0.772
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
59.209
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.657
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.778
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 47.739
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.555
After features/support/hooks.rb:326 0.672
After features/support/hooks.rb:100 0.000