Project Number Date
test_Tails_ISO_stable 5070 04 Sep 2024, 18:25

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 21:6.982 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:35.703
Before features/support/hooks.rb:269 0.003
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.341
When I start Tails from USB drive "old" with network unplugged 1:57.137
Then the boot device has safe access rights 3.744
And Tails is running from USB drive "old" 0.433
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:326 3.629
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.086
Before features/support/hooks.rb:269 0.005
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login 1:25.032
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 36.135
And I take note of which tps features are available 2.119
Then a Tails persistence partition exists on USB drive "old" 1.002
And I shutdown Tails and wait for the computer to power off 9.198
After features/support/hooks.rb:326 0.227
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.165
Before features/support/hooks.rb:269 0.007
Given a computer 0.871
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.722
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.100
When I write some files expected to persist 2.023
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.526
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.465
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.969
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.469
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 26.802
And I log in to a new session 19.751
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.007
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.321
Then the running Tails is installed on USB drive "to_upgrade" 21.690
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 2.786
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.454
Before features/support/hooks.rb:269 0.004
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.259
Then all tps features from the old Tails version are active 1.763
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.713
And the expected persistent files created with the old Tails version are present in the filesystem 1.623
And all persistent directories from the old Tails version have safe access rights 2.487
After features/support/hooks.rb:326 0.760
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:3.940
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.584
And no SquashFS delta is installed 0.519
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.094
And Tor is ready 20.193
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.613
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.872
Given I shutdown Tails and wait for the computer to power off 11.676
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.436
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.957
And the file system changes introduced in version 6.2~testoverlayfs are present 0.417
And only the 6.2~testoverlayfs SquashFS delta is installed 0.121
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.378
# 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.429
When the network is plugged 0.093
And Tor is ready 20.958
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.301
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.315
Given I shutdown Tails and wait for the computer to power off 4.332
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.829
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.284
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.395
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.073
And Tor is ready 16.941
Then the Upgrader considers the system as up-to-date 0.334
# 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.438
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.139
After features/support/hooks.rb:326 0.786
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
59.162
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.579
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.511
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 1.224
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 45.122
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.566
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.000