Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 79 21 Oct 2024, 07:36

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:31.195 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:28.284
Before features/support/hooks.rb:269 0.005
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.144
When I start Tails from USB drive "old" with network unplugged 1:50.959
Then the boot device has safe access rights 3.730
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.372
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 7.556
After features/support/hooks.rb:100 0.013
Tags: @product
2:16.432
Before features/support/hooks.rb:269 0.007
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:31.804
Then Tails is running from USB drive "old" 0.449
And I create a persistent partition 34.069
And I take note of which tps features are available 2.084
Then a Tails persistence partition exists on USB drive "old" 0.933
And I shutdown Tails and wait for the computer to power off 6.851
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.008
Tags: @product
3:1.310
Before features/support/hooks.rb:269 0.005
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.994
Then Tails is running from USB drive "old" 0.432
And all tps features are active 2.161
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.494
And all persistent directories from the old Tails version have safe access rights 3.354
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 4.492
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.598
After features/support/hooks.rb:326 0.240
After features/support/hooks.rb:100 0.011
Tags: @product
2:39.851
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.306
And I log in to a new session 22.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.925
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.214
Then the running Tails is installed on USB drive "to_upgrade" 19.403
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:326 2.803
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.522
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.990
Then all tps features from the old Tails version are active 2.016
And Tails is running from USB drive "to_upgrade" 0.455
And the boot device has safe access rights 3.962
And the expected persistent files created with the old Tails version are present in the filesystem 1.802
And all persistent directories from the old Tails version have safe access rights 3.081
After features/support/hooks.rb:326 0.994
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:1.358
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 14.485
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.130
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.073
And Tor is ready 48.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.612
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.480
Given I shutdown Tails and wait for the computer to power off 8.881
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.524
Then Tails is running version 6.2~testoverlayfs 0.058
And all tps features are active 2.358
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.348
When the network is plugged 0.078
And Tor is ready 19.515
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.615
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.600
Given I shutdown Tails and wait for the computer to power off 4.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.645
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.196
And the file system changes introduced in version 6.3~testoverlayfs are present 0.556
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.386
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.098
And Tor is ready 20.759
Then the Upgrader considers the system as up-to-date 0.330
# 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.231
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.964
After features/support/hooks.rb:326 0.950
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.434
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.904
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.873
But a current signing key is available on our website 0.000
When the network is plugged 0.178
And Tor is ready 19.185
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.924
After features/support/hooks.rb:326 0.860
After features/support/hooks.rb:100 0.000