Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 57 27 Sep 2024, 07:21

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:26.904 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
1:50.294
Before features/support/hooks.rb:269 0.004
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.634
When I start Tails from USB drive "old" with network unplugged 1:15.152
Then the boot device has safe access rights 3.110
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 6.683
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.863
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:24.408
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 31.156
And I take note of which tps features are available 1.405
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.529
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
3:8.881
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.217
Then Tails is running from USB drive "old" 0.450
And all tps features are active 2.483
When I write some files expected to persist 2.473
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.776
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 4.403
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.750
After features/support/hooks.rb:326 0.294
After features/support/hooks.rb:100 0.177
Tags: @product
2:31.246
Before features/support/hooks.rb:269 0.084
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.755
And I log in to a new session 21.145
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.344
And I plug USB drive "to_upgrade" 2.379
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.024
Then the running Tails is installed on USB drive "to_upgrade" 18.068
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.291
After features/support/hooks.rb:326 1.919
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.162
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.933
Then all tps features from the old Tails version are active 1.650
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.464
And the expected persistent files created with the old Tails version are present in the filesystem 1.623
And all persistent directories from the old Tails version have safe access rights 2.894
After features/support/hooks.rb:326 1.367
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:13.896
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 15.564
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.473
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.549
When the network is plugged 0.104
And Tor is ready 26.924
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.926
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.412
Given I shutdown Tails and wait for the computer to power off 11.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.934
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.650
And the file system changes introduced in version 6.2~testoverlayfs are present 0.374
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.402
When the network is plugged 0.077
And Tor is ready 16.358
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.502
Given I shutdown Tails and wait for the computer to power off 4.771
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.089
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.421
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.069
And Tor is ready 16.624
Then the Upgrader considers the system as up-to-date 10.900
# 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.541
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.011
After features/support/hooks.rb:326 1.042
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
1:9.560
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 13.732
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.248
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.780
But a current signing key is available on our website 0.000
When the network is plugged 0.171
And Tor is ready 52.898
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.649
After features/support/hooks.rb:326 1.010
After features/support/hooks.rb:100 0.000