Project Number Date
test_Tails_ISO_devel 3262 31 Jan 2024, 12:27

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 88 0 0 0 0 88 7 0 7 18:27.714 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:33.017
Before features/support/hooks.rb:245 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 19.221
When I start Tails from USB drive "old" with network unplugged 1:8.593
Then the boot device has safe access rights 2.770
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.431
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:291 3.513
After features/support/hooks.rb:75 0.009
Tags: @product
2:18.024
Before features/support/hooks.rb:245 0.006
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:27.743
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 39.494
And I take note of which tps features are available 1.499
Then a Tails persistence partition exists on USB drive "old" 0.714
And I shutdown Tails and wait for the computer to power off 8.082
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.008
Tags: @product
2:40.827
Before features/support/hooks.rb:245 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.320
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.885
When I write some files expected to persist 1.636
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 2.125
And I take note of which tps features are available 0.382
And I shutdown Tails and wait for the computer to power off 4.065
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.385
After features/support/hooks.rb:291 0.095
After features/support/hooks.rb:75 0.009
Tags: @product
2:30.986
Before features/support/hooks.rb:245 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.125
And I log in to a new session 17.217
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.147
And I plug USB drive "to_upgrade" 2.384
And I cancel the GNOME authentication prompt 1.701
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.370
Then the running Tails is installed on USB drive "to_upgrade" 12.655
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:291 3.560
After features/support/hooks.rb:75 0.000
Tags: @product
2:23.704
Before features/support/hooks.rb:245 0.005
Given a computer 0.162
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.318
Then all tps features from the old Tails version are active 1.428
And Tails is running from USB drive "to_upgrade" 0.406
And the boot device has safe access rights 2.922
And the expected persistent files created with the old Tails version are present in the filesystem 1.259
And all persistent directories from the old Tails version have safe access rights 2.206
After features/support/hooks.rb:291 0.972
After features/support/hooks.rb:75 0.007
Tags: @product @automatic_upgrade
6:29.399
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.739
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.044
And Tor is ready 20.040
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.519
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.852
Given I shutdown Tails and wait for the computer to power off 6.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.173
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.896
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.260
When the network is plugged 0.053
And Tor is ready 18.798
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.602
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.310
Given I shutdown Tails and wait for the computer to power off 4.743
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.000
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.001
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.036
And Tor is ready 20.302
Then the Upgrader considers the system as up-to-date 0.227
# 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.687
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.975
After features/support/hooks.rb:291 0.773
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
31.756
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.900
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
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.453
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 17.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.596
After features/support/hooks.rb:291 0.606
After features/support/hooks.rb:75 0.000