Project Number Date
test_Tails_ISO_devel 3473 10 Aug 2024, 12:13

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 18:23.452 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:7.964
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.168
When I start Tails from USB drive "old" with network unplugged 1:33.695
Then the boot device has safe access rights 2.897
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:326 1.130
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.684
Before features/support/hooks.rb:269 0.004
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:20.192
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 30.445
And I take note of which tps features are available 1.529
Then a Tails persistence partition exists on USB drive "old" 0.770
And I shutdown Tails and wait for the computer to power off 8.251
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.007
Tags: @product
2:49.055
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.728
Then Tails is running from USB drive "old" 0.313
And all tps features are active 2.038
When I write some files expected to persist 1.920
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.279
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.292
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.233
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.482
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 10.910
And I log in to a new session 27.147
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.671
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.449
Then the running Tails is installed on USB drive "to_upgrade" 18.471
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:326 7.078
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.835
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.991
Then all tps features from the old Tails version are active 1.548
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 2.895
And the expected persistent files created with the old Tails version are present in the filesystem 1.346
And all persistent directories from the old Tails version have safe access rights 2.512
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:8.832
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.883
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.060
And Tor is ready 21.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.419
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.498
Given I shutdown Tails and wait for the computer to power off 8.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.333
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.279
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs 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.357
# 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.293
When the network is plugged 0.080
And Tor is ready 15.588
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.199
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.366
Given I shutdown Tails and wait for the computer to power off 4.268
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.958
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.428
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.075
And Tor is ready 16.930
Then the Upgrader considers the system as up-to-date 10.854
# 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.225
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.908
After features/support/hooks.rb:326 0.713
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
36.597
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.039
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.810
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 17.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.717
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.000