Project Number Date
test_Tails_ISO_stable 4709 11 Mar 2024, 17: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:20.515 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:41.107
Before features/support/hooks.rb:245 0.005
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 19.950
When I start Tails from USB drive "old" with network unplugged 1:15.975
Then the boot device has safe access rights 2.853
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:291 6.903
After features/support/hooks.rb:75 0.008
Tags: @product
2:4.755
Before features/support/hooks.rb:245 0.004
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:15.360
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 39.285
And I take note of which tps features are available 1.888
Then a Tails persistence partition exists on USB drive "old" 0.695
And I shutdown Tails and wait for the computer to power off 7.041
After features/support/hooks.rb:291 0.185
After features/support/hooks.rb:75 0.009
Tags: @product
2:37.733
Before features/support/hooks.rb:245 0.005
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.006
Then Tails is running from USB drive "old" 0.322
And all tps features are active 1.930
When I write some files expected to persist 1.574
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.473
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.096
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.093
After features/support/hooks.rb:291 0.172
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.137
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.087
And I log in to a new session 15.120
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.501
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.750
Then the running Tails is installed on USB drive "to_upgrade" 13.838
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.181
After features/support/hooks.rb:291 3.576
After features/support/hooks.rb:75 0.000
Tags: @product
2:18.239
Before features/support/hooks.rb:245 0.012
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.721
Then all tps features from the old Tails version are active 1.479
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.889
And the expected persistent files created with the old Tails version are present in the filesystem 1.393
And all persistent directories from the old Tails version have safe access rights 2.278
After features/support/hooks.rb:291 0.783
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:32.010
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 12.434
And no SquashFS delta is installed 0.118
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.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.028
And Tor is ready 20.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.193
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.158
Given I shutdown Tails and wait for the computer to power off 7.081
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.874
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.221
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.236
When the network is plugged 0.037
And Tor is ready 17.518
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.510
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.901
Given I shutdown Tails and wait for the computer to power off 4.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.873
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.767
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.282
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.037
And Tor is ready 17.369
Then the Upgrader considers the system as up-to-date 0.222
# 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.398
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.885
After features/support/hooks.rb:291 0.868
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
36.530
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.919
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
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 1.520
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 17.069
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.664
After features/support/hooks.rb:291 0.688
After features/support/hooks.rb:75 0.000