Project Number Date
test_Tails_ISO_stable 4612 10 Jan 2024, 19:26

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 17:46.430 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:43.432
Before features/support/hooks.rb:245 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 18.896
When I start Tails from USB drive "old" with network unplugged 1:18.781
Then the boot device has safe access rights 3.300
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.397
After features/support/hooks.rb:291 6.517
After features/support/hooks.rb:75 0.010
Tags: @product
2:4.491
Before features/support/hooks.rb:245 0.007
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:7.524
Then Tails is running from USB drive "old" 0.530
And I create a persistent partition 44.664
And I take note of which tps features are available 1.472
Then a Tails persistence partition exists on USB drive "old" 0.885
And I shutdown Tails and wait for the computer to power off 9.226
After features/support/hooks.rb:291 0.106
After features/support/hooks.rb:75 0.009
Tags: @product
2:29.675
Before features/support/hooks.rb:245 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.416
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.237
When I write some files expected to persist 1.976
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.636
And all persistent directories from the old Tails version have safe access rights 2.848
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 3.068
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.246
After features/support/hooks.rb:291 0.130
After features/support/hooks.rb:75 0.010
Tags: @product
2:37.579
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.214
And I log in to a new session 17.245
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.265
And I plug USB drive "to_upgrade" 2.630
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.093
Then the running Tails is installed on USB drive "to_upgrade" 13.666
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:291 6.657
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.942
Before features/support/hooks.rb:245 0.008
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.602
Then all tps features from the old Tails version are active 1.832
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.873
And the expected persistent files created with the old Tails version are present in the filesystem 1.824
And all persistent directories from the old Tails version have safe access rights 3.204
After features/support/hooks.rb:291 0.933
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
6:19.716
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 28.389
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.292
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.392
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.593
When the network is plugged 0.043
And Tor is ready 16.827
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.764
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.685
Given I shutdown Tails and wait for the computer to power off 8.469
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.354
Then Tails is running version 2.2~testoverlayfsng 0.128
And all tps features are active 2.682
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.447
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.288
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.371
When the network is plugged 0.042
And Tor is ready 20.634
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.629
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.209
Given I shutdown Tails and wait for the computer to power off 4.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.286
Then Tails is running version 2.3~testoverlayfsng 0.128
And all tps features are active 2.498
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.609
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.098
# 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.330
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.417
When the network is plugged 0.049
And Tor is ready 17.462
Then the Upgrader considers the system as up-to-date 0.466
# 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 26.452
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.349
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
26.593
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 9.477
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.361
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the signing key used by the Upgrader is outdated 0.541
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 13.374
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.729
After features/support/hooks.rb:291 1.203
After features/support/hooks.rb:75 0.000