Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 19 19 Aug 2024, 07:14

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:14.172 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:34.790
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 29.844
When I start Tails from USB drive "old" with network unplugged 1:59.244
Then the boot device has safe access rights 3.319
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.240
After features/support/hooks.rb:326 6.980
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.186
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:20.880
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 32.689
And I take note of which tps features are available 1.659
Then a Tails persistence partition exists on USB drive "old" 1.019
And I shutdown Tails and wait for the computer to power off 8.362
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.791
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.840
Then Tails is running from USB drive "old" 0.404
And all tps features are active 2.035
When I write some files expected to persist 2.072
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.317
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.871
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 4.383
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.818
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.578
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 12.640
And I log in to a new session 20.559
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.505
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.841
Then the running Tails is installed on USB drive "to_upgrade" 22.237
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 2.239
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.232
Before features/support/hooks.rb:269 0.007
Given a computer 0.268
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.685
Then all tps features from the old Tails version are active 1.676
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.530
And the expected persistent files created with the old Tails version are present in the filesystem 1.396
And all persistent directories from the old Tails version have safe access rights 2.342
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:19.733
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 13.482
And no SquashFS delta is installed 0.246
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.737
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.090
And Tor is ready 24.027
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.761
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.922
Given I shutdown Tails and wait for the computer to power off 10.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.243
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.280
When the network is plugged 0.070
And Tor is ready 16.051
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.311
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.475
Given I shutdown Tails and wait for the computer to power off 4.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.200
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.983
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.066
And Tor is ready 17.539
Then the Upgrader considers the system as up-to-date 0.370
# 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.022
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.133
After features/support/hooks.rb:326 0.852
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
32.860
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.226
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.107
And the signing key used by the Upgrader is outdated 0.729
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 17.916
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.542
After features/support/hooks.rb:326 0.975
After features/support/hooks.rb:100 0.000