Project Number Date
test_Tails_ISO_tor-blog-40076-bring-back-download-links 7 20 Oct 2024, 16:06

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 18:47.898 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:17.281
Before features/support/hooks.rb:269 0.004
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.117
When I start Tails from USB drive "old" with network unplugged 1:42.045
Then the boot device has safe access rights 2.862
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.691
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.402
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:23.739
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 30.439
And I take note of which tps features are available 1.399
Then a Tails persistence partition exists on USB drive "old" 0.779
And I shutdown Tails and wait for the computer to power off 8.560
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.060
Before features/support/hooks.rb:269 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.985
Then Tails is running from USB drive "old" 0.429
And all tps features are active 2.084
When I write some files expected to persist 1.608
# 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.358
And all persistent directories from the old Tails version have safe access rights 2.413
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.377
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.960
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.007
Tags: @product
2:26.024
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 10.198
And I log in to a new session 17.889
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.488
And I plug USB drive "to_upgrade" 2.510
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.583
Then the running Tails is installed on USB drive "to_upgrade" 18.947
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 1.898
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.826
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.721
Then all tps features from the old Tails version are active 1.620
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 3.053
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.549
After features/support/hooks.rb:326 0.972
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:21.762
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 11.318
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.091
And Tor is ready 21.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.461
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.842
Given I shutdown Tails and wait for the computer to power off 8.384
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.941
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.331
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.261
When the network is plugged 0.066
And Tor is ready 16.650
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.471
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.300
Given I shutdown Tails and wait for the computer to power off 4.673
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.895
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.961
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.072
And Tor is ready 18.462
Then the Upgrader considers the system as up-to-date 0.307
# 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 13.513
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.844
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.540
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.216
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 1.397
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 18.002
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.499
After features/support/hooks.rb:326 0.657
After features/support/hooks.rb:100 0.000