Project Number Date
test_Tails_ISO_stable 5041 22 Aug 2024, 12:38

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:53.037 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:4.561
Before features/support/hooks.rb:269 0.004
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.426
When I start Tails from USB drive "old" with network unplugged 1:30.869
Then the boot device has safe access rights 2.976
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.485
After features/support/hooks.rb:100 0.027
Tags: @product
2:5.896
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:23.326
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 31.348
And I take note of which tps features are available 1.621
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 8.172
After features/support/hooks.rb:326 0.255
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.243
Before features/support/hooks.rb:269 0.006
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.915
Then Tails is running from USB drive "old" 0.350
And all tps features are active 2.207
When I write some files expected to persist 2.048
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.381
And I take note of which tps features are available 0.506
And I shutdown Tails and wait for the computer to power off 4.451
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.551
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.636
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 11.944
And I log in to a new session 19.578
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.630
And I plug USB drive "to_upgrade" 2.460
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.587
Then the running Tails is installed on USB drive "to_upgrade" 20.005
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.685
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.634
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.925
Then all tps features from the old Tails version are active 1.778
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.616
And the expected persistent files created with the old Tails version are present in the filesystem 1.461
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:26.224
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 12.366
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.099
And Tor is ready 20.295
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.440
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.691
Given I shutdown Tails and wait for the computer to power off 11.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.205
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.139
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.065
And Tor is ready 16.824
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.180
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.059
Given I shutdown Tails and wait for the computer to power off 4.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.554
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.059
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.080
And Tor is ready 17.466
Then the Upgrader considers the system as up-to-date 10.800
# 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.119
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.960
After features/support/hooks.rb:326 0.795
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.840
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 9.761
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.431
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.864
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 20.857
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.777
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.000