Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 60 30 Sep 2024, 07:11

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:17.194 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.429
Before features/support/hooks.rb:269 0.007
Given a computer 0.218
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" 30.553
When I start Tails from USB drive "old" with network unplugged 1:32.240
Then the boot device has safe access rights 3.246
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 7.162
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.835
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:23.888
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 31.597
And I take note of which tps features are available 1.798
Then a Tails persistence partition exists on USB drive "old" 0.711
And I shutdown Tails and wait for the computer to power off 8.290
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.915
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 with persistence enabled 2:12.621
Then Tails is running from USB drive "old" 0.456
And all tps features are active 1.959
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.654
And I take note of which tps features are available 0.547
And I shutdown Tails and wait for the computer to power off 4.366
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.633
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.042
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 12.421
And I log in to a new session 20.291
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.778
And I plug USB drive "to_upgrade" 2.489
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.192
Then the running Tails is installed on USB drive "to_upgrade" 22.433
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 1.970
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.048
Before features/support/hooks.rb:269 0.008
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.564
Then all tps features from the old Tails version are active 1.621
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 3.378
And the expected persistent files created with the old Tails version are present in the filesystem 1.434
And all persistent directories from the old Tails version have safe access rights 2.525
After features/support/hooks.rb:326 0.819
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:39.255
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 12.950
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
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.397
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.138
And Tor is ready 18.772
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.703
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.573
Given I shutdown Tails and wait for the computer to power off 8.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.650
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.706
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# 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.438
When the network is plugged 0.122
And Tor is ready 22.914
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.674
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.523
Given I shutdown Tails and wait for the computer to power off 4.352
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.085
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.977
And the file system changes introduced in version 6.3~testoverlayfs are present 0.684
And only the 6.3~testoverlayfs SquashFS delta is installed 0.118
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.414
When the network is plugged 0.066
And Tor is ready 19.624
Then the Upgrader considers the system as up-to-date 0.289
# 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.653
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.002
After features/support/hooks.rb:326 0.779
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
38.666
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.424
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.626
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the signing key used by the Upgrader is outdated 0.816
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 20.006
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.598
After features/support/hooks.rb:326 0.911
After features/support/hooks.rb:100 0.000