Project Number Date
test_Tails_ISO_stable 5043 24 Aug 2024, 12:22

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:52.595 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:5.873
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.196
When I start Tails from USB drive "old" with network unplugged 1:29.173
Then the boot device has safe access rights 3.179
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 3.712
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.299
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:24.254
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 32.735
And I take note of which tps features are available 1.434
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.475
After features/support/hooks.rb:326 0.173
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.229
Before features/support/hooks.rb:269 0.007
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.123
Then Tails is running from USB drive "old" 0.328
And all tps features are active 2.108
When I write some files expected to persist 1.699
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.277
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.708
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.351
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.602
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.104
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.184
And I log in to a new session 18.124
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.522
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.154
Then the running Tails is installed on USB drive "to_upgrade" 22.306
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 2.030
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.849
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.361
Then all tps features from the old Tails version are active 1.552
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.532
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:326 0.582
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:35.855
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 11.752
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.538
When the network is plugged 0.066
And Tor is ready 20.252
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.506
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.559
Given I shutdown Tails and wait for the computer to power off 8.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.460
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
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.311
# 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.252
When the network is plugged 0.081
And Tor is ready 17.938
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.808
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.264
Given I shutdown Tails and wait for the computer to power off 4.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.531
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.969
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.384
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.089
And Tor is ready 17.634
Then the Upgrader considers the system as up-to-date 10.787
# 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.773
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.876
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
34.383
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.399
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.914
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 16.760
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.801
After features/support/hooks.rb:326 1.364
After features/support/hooks.rb:100 0.000