Project Number Date
test_Tails_ISO_devel 3496 29 Aug 2024, 12:29

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:47.970 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:59.373
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.755
When I start Tails from USB drive "old" with network unplugged 1:24.518
Then the boot device has safe access rights 2.876
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 9.000
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.889
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:23.774
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 30.954
And I take note of which tps features are available 1.456
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 8.323
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.011
Tags: @product
2:55.471
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.517
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.090
When I write some files expected to persist 1.739
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.509
And all persistent directories from the old Tails version have safe access rights 2.574
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.310
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.467
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.132
Before features/support/hooks.rb:269 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 11.625
And I log in to a new session 17.868
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.402
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.352
Then the running Tails is installed on USB drive "to_upgrade" 19.034
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 0.987
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.540
Before features/support/hooks.rb:269 0.007
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.422
Then all tps features from the old Tails version are active 1.556
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.101
And the expected persistent files created with the old Tails version are present in the filesystem 1.379
And all persistent directories from the old Tails version have safe access rights 2.526
After features/support/hooks.rb:326 0.616
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:32.871
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.825
And no SquashFS delta is installed 0.308
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.845
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.097
And Tor is ready 19.380
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.515
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.147
Given I shutdown Tails and wait for the computer to power off 10.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.501
Then Tails is running version 6.2~testoverlayfs 0.027
And all tps features are active 2.159
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.266
When the network is plugged 0.086
And Tor is ready 19.377
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.285
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.700
Given I shutdown Tails and wait for the computer to power off 4.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.697
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.035
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.072
And Tor is ready 17.748
Then the Upgrader considers the system as up-to-date 10.765
# 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.553
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.925
After features/support/hooks.rb:326 0.786
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.691
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.832
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.764
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.102
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.549
After features/support/hooks.rb:326 0.782
After features/support/hooks.rb:100 0.000