Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 59 29 Sep 2024, 07:13

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:19.839 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:14.646
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 30.406
When I start Tails from USB drive "old" with network unplugged 1:38.762
Then the boot device has safe access rights 3.124
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 3.773
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.376
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:21.746
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 30.521
And I take note of which tps features are available 1.491
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.247
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.144
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.468
Then Tails is running from USB drive "old" 0.319
And all tps features are active 2.075
When I write some files expected to persist 1.770
# 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.382
And all persistent directories from the old Tails version have safe access rights 2.580
And I take note of which tps features are available 0.521
And I shutdown Tails and wait for the computer to power off 4.745
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.845
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.012
Tags: @product
2:30.274
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.065
And I log in to a new session 19.601
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.549
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.120
Then the running Tails is installed on USB drive "to_upgrade" 21.047
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:326 3.090
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.427
Before features/support/hooks.rb:269 0.007
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.166
Then all tps features from the old Tails version are active 1.621
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.289
And the expected persistent files created with the old Tails version are present in the filesystem 1.427
And all persistent directories from the old Tails version have safe access rights 2.401
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:40.327
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.824
And no SquashFS delta is installed 0.215
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.354
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.083
And Tor is ready 22.708
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.782
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.988
Given I shutdown Tails and wait for the computer to power off 13.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.277
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.141
And the file system changes introduced in version 6.2~testoverlayfs are present 0.427
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.494
# 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.337
When the network is plugged 0.072
And Tor is ready 19.802
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.567
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.424
Given I shutdown Tails and wait for the computer to power off 4.215
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.954
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.286
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.069
And Tor is ready 15.029
Then the Upgrader considers the system as up-to-date 0.379
# 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.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.157
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.643
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 10.823
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.016
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 19.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.609
After features/support/hooks.rb:326 0.903
After features/support/hooks.rb:100 0.000