Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 55 26 Sep 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:39.212 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:27.461
Before features/support/hooks.rb:269 0.007
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.454
When I start Tails from USB drive "old" with network unplugged 1:48.041
Then the boot device has safe access rights 3.575
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 7.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.795
Before features/support/hooks.rb:269 0.005
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:25.630
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 32.134
And I take note of which tps features are available 2.026
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 8.496
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.541
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.042
Then Tails is running from USB drive "old" 0.321
And all tps features are active 3.180
When I write some files expected to persist 1.818
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 2.652
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 4.405
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.710
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.322
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.783
And I log in to a new session 23.251
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.233
And I plug USB drive "to_upgrade" 2.729
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.681
Then the running Tails is installed on USB drive "to_upgrade" 21.125
And I unplug USB drive "to_upgrade" 0.282
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 6.922
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.016
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.954
Then all tps features from the old Tails version are active 1.831
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.323
And the expected persistent files created with the old Tails version are present in the filesystem 1.627
And all persistent directories from the old Tails version have safe access rights 2.725
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:18.287
Before features/support/hooks.rb:269 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.642
And no SquashFS delta is installed 0.404
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.646
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.376
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.613
When the network is plugged 0.086
And Tor is ready 48.640
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.686
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.458
Given I shutdown Tails and wait for the computer to power off 13.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.063
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.435
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.285
When the network is plugged 0.091
And Tor is ready 18.040
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.085
Given I shutdown Tails and wait for the computer to power off 4.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.881
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.579
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.382
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.457
When the network is plugged 0.086
And Tor is ready 19.389
Then the Upgrader considers the system as up-to-date 0.309
# 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 16.068
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.170
After features/support/hooks.rb:326 1.007
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
39.788
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.677
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 1.008
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 21.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.635
After features/support/hooks.rb:326 0.941
After features/support/hooks.rb:100 0.000