Project Number Date
test_Tails_ISO_stable 5127 30 Sep 2024, 18:26

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 20:29.204 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:8.238
Before features/support/hooks.rb:269 0.005
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.423
When I start Tails from USB drive "old" with network unplugged 1:32.002
Then the boot device has safe access rights 3.092
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.694
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 7.241
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.454
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:26.318
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 33.602
And I take note of which tps features are available 1.682
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.480
After features/support/hooks.rb:326 0.193
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.472
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.314
Then Tails is running from USB drive "old" 1.306
And all tps features are active 2.472
When I write some files expected to persist 2.903
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 2.865
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 4.594
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.540
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.226
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.875
And I log in to a new session 21.372
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.855
And I plug USB drive "to_upgrade" 2.481
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.959
Then the running Tails is installed on USB drive "to_upgrade" 27.230
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.873
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.560
Before features/support/hooks.rb:269 0.011
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.706
Then all tps features from the old Tails version are active 1.976
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 3.821
And the expected persistent files created with the old Tails version are present in the filesystem 1.714
And all persistent directories from the old Tails version have safe access rights 2.691
After features/support/hooks.rb:326 0.996
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:57.377
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 14.640
And no SquashFS delta is installed 0.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.564
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.357
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.084
And Tor is ready 27.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.046
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.764
Given I shutdown Tails and wait for the computer to power off 11.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.255
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.360
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.254
When the network is plugged 0.071
And Tor is ready 19.253
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.092
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.620
Given I shutdown Tails and wait for the computer to power off 6.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.667
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.620
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.075
And Tor is ready 18.140
Then the Upgrader considers the system as up-to-date 0.337
# 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.898
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.176
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
41.874
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.792
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.505
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.862
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 22.395
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.191
After features/support/hooks.rb:326 0.782
After features/support/hooks.rb:100 0.000