Project Number Date
test_Tails_ISO_20522-ocr-more 8 18 Dec 2024, 05:18

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 19:56.712 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:8.265
Before features/support/hooks.rb:269 0.005
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.842
When I start Tails from USB drive "old" with network unplugged 1:33.180
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.783
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.027
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:24.578
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 34.412
And I take note of which tps features are available 1.574
Then a Tails persistence partition exists on USB drive "old" 0.727
And I shutdown Tails and wait for the computer to power off 8.183
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.585
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.382
Then Tails is running from USB drive "old" 1.568
And all tps features are active 1.907
When I write some files expected to persist 1.551
# 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.358
And all persistent directories from the old Tails version have safe access rights 2.673
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.224
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.038
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.007
Tags: @product
2:37.172
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 11.657
And I log in to a new session 22.247
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.540
And I plug USB drive "to_upgrade" 4.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.789
Then the running Tails is installed on USB drive "to_upgrade" 24.269
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 3.531
After features/support/hooks.rb:100 0.000
Tags: @product
2:2.785
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.434
Then all tps features from the old Tails version are active 1.646
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.258
And the expected persistent files created with the old Tails version are present in the filesystem 1.550
And all persistent directories from the old Tails version have safe access rights 2.379
After features/support/hooks.rb:326 1.293
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:35.750
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 14.364
And no SquashFS delta is installed 0.281
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.619
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.075
And Tor is ready 19.158
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.664
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.367
Given I shutdown Tails and wait for the computer to power off 1:23.699
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.328
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.558
And the file system changes introduced in version 6.2~testoverlayfs are present 0.356
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.383
When the network is plugged 0.076
And Tor is ready 19.500
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.459
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.647
Given I shutdown Tails and wait for the computer to power off 4.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.573
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.105
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.165
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.371
And Tor is ready 17.541
Then the Upgrader considers the system as up-to-date 10.893
# 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 15.724
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.109
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.126
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 9.873
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.790
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.703
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.056
After features/support/hooks.rb:326 0.631
After features/support/hooks.rb:100 0.000