Project Number Date
test_Tails_ISO_stable 4732 20 Mar 2024, 16:11

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:9.423 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:34.085
Before features/support/hooks.rb:245 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 20.644
When I start Tails from USB drive "old" with network unplugged 1:8.329
Then the boot device has safe access rights 2.858
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:291 3.529
After features/support/hooks.rb:75 0.009
Tags: @product
2:8.766
Before features/support/hooks.rb:245 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:27.865
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 32.245
And I take note of which tps features are available 1.390
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 6.018
After features/support/hooks.rb:291 0.115
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.551
Before features/support/hooks.rb:245 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.574
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.916
When I write some files expected to persist 1.957
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.527
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.018
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.844
After features/support/hooks.rb:291 0.139
After features/support/hooks.rb:75 0.011
Tags: @product
2:18.348
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.094
And I log in to a new session 16.164
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.648
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.567
Then the running Tails is installed on USB drive "to_upgrade" 13.052
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:291 3.567
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.398
Before features/support/hooks.rb:245 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.378
Then all tps features from the old Tails version are active 1.458
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.090
And the expected persistent files created with the old Tails version are present in the filesystem 1.503
And all persistent directories from the old Tails version have safe access rights 2.442
After features/support/hooks.rb:291 0.781
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:29.584
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.930
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.050
And Tor is ready 19.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.462
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.387
Given I shutdown Tails and wait for the computer to power off 7.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.111
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.103
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.244
When the network is plugged 0.033
And Tor is ready 45.609
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.591
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.175
Given I shutdown Tails and wait for the computer to power off 4.224
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.185
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.033
And Tor is ready 16.180
Then the Upgrader considers the system as up-to-date 10.660
# 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.753
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.807
After features/support/hooks.rb:291 0.738
After features/support/hooks.rb:75 0.049
Tags: @product @automatic_upgrade
56.687
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.208
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.449
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.513
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 44.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.614
After features/support/hooks.rb:291 0.854
After features/support/hooks.rb:75 0.000