Project Number Date
test_Tails_ISO_stable 5263 14 Nov 2024, 08:44

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:15.779 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:19.610
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.615
When I start Tails from USB drive "old" with network unplugged 1:40.712
Then the boot device has safe access rights 2.965
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.570
After features/support/hooks.rb:100 0.025
Tags: @product
2:15.521
Before features/support/hooks.rb:269 0.005
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login 1:31.844
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 32.341
And I take note of which tps features are available 1.454
Then a Tails persistence partition exists on USB drive "old" 0.781
And I shutdown Tails and wait for the computer to power off 8.546
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.019
Tags: @product
2:53.891
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.227
Then Tails is running from USB drive "old" 0.392
And all tps features are active 2.045
When I write some files expected to persist 1.809
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.729
And I take note of which tps features are available 0.611
And I shutdown Tails and wait for the computer to power off 4.448
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.861
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.013
Tags: @product
2:40.690
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.058
And I log in to a new session 22.249
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.807
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.058
Then the running Tails is installed on USB drive "to_upgrade" 19.605
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 3.580
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.936
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.104
Then all tps features from the old Tails version are active 2.013
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.377
And the expected persistent files created with the old Tails version are present in the filesystem 1.456
And all persistent directories from the old Tails version have safe access rights 2.443
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:9.895
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 12.646
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.579
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.133
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.371
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.071
And Tor is ready 20.620
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.641
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.207
Given I shutdown Tails and wait for the computer to power off 11.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.563
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.382
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.285
When the network is plugged 0.083
And Tor is ready 47.798
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.652
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.934
Given I shutdown Tails and wait for the computer to power off 4.457
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.438
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.283
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.370
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.120
And Tor is ready 20.153
Then the Upgrader considers the system as up-to-date 0.319
# 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.976
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.227
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
36.234
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.446
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.700
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.776
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 17.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.643
After features/support/hooks.rb:326 1.073
After features/support/hooks.rb:100 0.000