Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 37 06 Sep 2024, 07:15

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:21.086 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:28.788
Before features/support/hooks.rb:269 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.392
When I start Tails from USB drive "old" with network unplugged 1:53.467
Then the boot device has safe access rights 3.463
And Tails is running from USB drive "old" 0.424
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:326 3.619
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.173
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:27.425
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 33.072
And I take note of which tps features are available 1.874
Then a Tails persistence partition exists on USB drive "old" 1.075
And I shutdown Tails and wait for the computer to power off 9.199
After features/support/hooks.rb:326 0.209
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.274
Before features/support/hooks.rb:269 0.007
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.210
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.298
When I write some files expected to persist 1.757
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.582
And all persistent directories from the old Tails version have safe access rights 3.119
And I take note of which tps features are available 0.657
And I shutdown Tails and wait for the computer to power off 4.208
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.552
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.197
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 16.081
And I log in to a new session 25.983
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.311
And I plug USB drive "to_upgrade" 2.543
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.027
Then the running Tails is installed on USB drive "to_upgrade" 24.747
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:326 2.918
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.258
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.350
Then all tps features from the old Tails version are active 1.981
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.396
And the expected persistent files created with the old Tails version are present in the filesystem 1.451
And all persistent directories from the old Tails version have safe access rights 2.545
After features/support/hooks.rb:326 0.710
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:49.244
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 13.800
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
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.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.553
When the network is plugged 0.084
And Tor is ready 19.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.994
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.138
Given I shutdown Tails and wait for the computer to power off 11.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.192
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.624
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.399
# 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.288
When the network is plugged 0.097
And Tor is ready 23.222
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.300
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.426
Given I shutdown Tails and wait for the computer to power off 4.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.052
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 3.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.604
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.442
And Tor is ready 21.341
Then the Upgrader considers the system as up-to-date 0.365
# 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.723
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.941
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.149
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 10.289
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 1.815
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 16.204
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.272
After features/support/hooks.rb:326 1.745
After features/support/hooks.rb:100 0.000