Project Number Date
test_Tails_ISO_stable 4605 08 Jan 2024, 16:15

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:32.502 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:26.314
Before features/support/hooks.rb:245 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 20.260
When I start Tails from USB drive "old" with network unplugged 1:0.445
Then the boot device has safe access rights 3.252
And Tails is running from USB drive "old" 0.429
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:291 3.562
After features/support/hooks.rb:75 0.013
Tags: @product
1:56.973
Before features/support/hooks.rb:245 0.010
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:4.256
Then Tails is running from USB drive "old" 0.445
And I create a persistent partition 42.548
And I take note of which tps features are available 1.628
Then a Tails persistence partition exists on USB drive "old" 0.747
And I shutdown Tails and wait for the computer to power off 7.153
After features/support/hooks.rb:291 0.117
After features/support/hooks.rb:75 0.009
Tags: @product
2:25.999
Before features/support/hooks.rb:245 0.007
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.527
Then Tails is running from USB drive "old" 0.369
And all tps features are active 2.114
When I write some files expected to persist 1.720
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.613
And all persistent directories from the old Tails version have safe access rights 2.796
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.221
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.680
After features/support/hooks.rb:291 0.135
After features/support/hooks.rb:75 0.008
Tags: @product
2:38.039
Before features/support/hooks.rb:245 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.005
And I log in to a new session 15.922
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.164
And I plug USB drive "to_upgrade" 2.501
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.603
Then the running Tails is installed on USB drive "to_upgrade" 13.434
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 2.123
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.864
Before features/support/hooks.rb:245 0.008
Given a computer 0.235
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.981
Then all tps features from the old Tails version are active 1.858
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.833
And the expected persistent files created with the old Tails version are present in the filesystem 1.760
And all persistent directories from the old Tails version have safe access rights 2.856
After features/support/hooks.rb:291 0.918
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:36.730
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.014
And no SquashFS delta is installed 0.214
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.363
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.074
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.371
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.637
When the network is plugged 0.041
And Tor is ready 15.136
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.907
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.903
Given I shutdown Tails and wait for the computer to power off 7.383
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.287
Then Tails is running version 2.2~testoverlayfsng 0.241
And all tps features are active 3.236
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.468
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.365
When the network is plugged 0.037
And Tor is ready 17.108
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.728
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.186
Given I shutdown Tails and wait for the computer to power off 4.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.331
Then Tails is running version 2.3~testoverlayfsng 0.131
And all tps features are active 2.637
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.684
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.118
# 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.331
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.314
When the network is plugged 0.048
And Tor is ready 44.899
Then the Upgrader considers the system as up-to-date 0.266
# 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 29.052
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.495
After features/support/hooks.rb:291 0.770
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
28.580
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.184
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.393
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.054
And the signing key used by the Upgrader is outdated 0.559
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 15.676
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.604
After features/support/hooks.rb:291 1.130
After features/support/hooks.rb:75 0.000