Project Number Date
test_Tails_ISO_stable 5038 20 Aug 2024, 12:31

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 20:20.997 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:14.030
Before features/support/hooks.rb:269 0.008
Given a computer 0.230
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.080
And I write an old version of the Tails USB image to disk "old" 31.192
When I start Tails from USB drive "old" with network unplugged 1:36.394
Then the boot device has safe access rights 3.873
And Tails is running from USB drive "old" 0.444
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 3.647
After features/support/hooks.rb:100 0.013
Tags: @product
2:21.226
Before features/support/hooks.rb:269 0.009
Given a computer 0.440
And I start Tails from USB drive "old" with network unplugged and I login 1:34.134
Then Tails is running from USB drive "old" 0.434
And I create a persistent partition 33.828
And I take note of which tps features are available 2.531
Then a Tails persistence partition exists on USB drive "old" 1.115
And I shutdown Tails and wait for the computer to power off 8.742
After features/support/hooks.rb:326 0.243
After features/support/hooks.rb:100 0.011
Tags: @product
3:5.834
Before features/support/hooks.rb:269 0.008
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.898
Then Tails is running from USB drive "old" 0.370
And all tps features are active 2.331
When I write some files expected to persist 2.172
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 3.334
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.377
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.884
After features/support/hooks.rb:326 0.225
After features/support/hooks.rb:100 0.013
Tags: @product
2:41.427
Before features/support/hooks.rb:269 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 12.366
And I log in to a new session 21.857
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.128
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.285
Then the running Tails is installed on USB drive "to_upgrade" 24.897
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 3.523
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.542
Before features/support/hooks.rb:269 0.008
Given a computer 0.447
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.527
Then all tps features from the old Tails version are active 1.772
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.980
And the expected persistent files created with the old Tails version are present in the filesystem 1.601
And all persistent directories from the old Tails version have safe access rights 2.859
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:57.063
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 12.326
And no SquashFS delta is installed 1.521
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.323
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.173
And Tor is ready 21.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.728
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.483
Given I shutdown Tails and wait for the computer to power off 9.040
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.518
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.649
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.438
# 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.319
When the network is plugged 0.148
And Tor is ready 18.466
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.501
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.201
Given I shutdown Tails and wait for the computer to power off 4.530
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.609
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.093
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.104
And Tor is ready 18.512
Then the Upgrader considers the system as up-to-date 0.411
# 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 15.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.111
After features/support/hooks.rb:326 0.832
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
38.871
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.037
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.499
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 1.011
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 20.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.322
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.000