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

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:41.509 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:18.869
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.151
When I start Tails from USB drive "old" with network unplugged 1:42.181
Then the boot device has safe access rights 3.219
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:326 3.551
After features/support/hooks.rb:100 0.011
Tags: @product
2:3.405
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:20.351
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 31.580
And I take note of which tps features are available 1.687
Then a Tails persistence partition exists on USB drive "old" 0.906
And I shutdown Tails and wait for the computer to power off 8.348
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.012
Tags: @product
2:55.432
Before features/support/hooks.rb:269 0.006
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.466
Then Tails is running from USB drive "old" 0.380
And all tps features are active 2.134
When I write some files expected to persist 2.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.341
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.744
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.112
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.081
After features/support/hooks.rb:326 0.098
After features/support/hooks.rb:100 0.011
Tags: @product
2:48.098
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 24.927
And I log in to a new session 19.972
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.797
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.851
Then the running Tails is installed on USB drive "to_upgrade" 22.631
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 3.510
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.871
Before features/support/hooks.rb:269 0.008
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.145
Then all tps features from the old Tails version are active 1.683
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.532
And the expected persistent files created with the old Tails version are present in the filesystem 1.500
And all persistent directories from the old Tails version have safe access rights 2.465
After features/support/hooks.rb:326 0.818
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:32.934
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 12.285
And no SquashFS delta is installed 0.199
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.112
And Tor is ready 24.686
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.760
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.130
Given I shutdown Tails and wait for the computer to power off 8.978
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.270
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.142
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.287
When the network is plugged 0.143
And Tor is ready 19.357
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.161
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.419
Given I shutdown Tails and wait for the computer to power off 4.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.287
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.070
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.410
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.083
And Tor is ready 19.377
Then the Upgrader considers the system as up-to-date 0.335
# 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.470
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.919
After features/support/hooks.rb:326 0.831
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
39.897
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.439
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.186
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.742
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 19.143
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.222
After features/support/hooks.rb:326 1.096
After features/support/hooks.rb:100 0.000