Project Number Date
test_Tails_ISO_sysadmin-17987-torbrowser-archive 3 19 Oct 2024, 05:36

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.719 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:12.195
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.074
When I start Tails from USB drive "old" with network unplugged 1:35.619
Then the boot device has safe access rights 3.169
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 7.179
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.955
Before features/support/hooks.rb:269 0.008
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login 1:25.927
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 32.412
And I take note of which tps features are available 1.532
Then a Tails persistence partition exists on USB drive "old" 0.867
And I shutdown Tails and wait for the computer to power off 8.652
After features/support/hooks.rb:326 0.198
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.213
Before features/support/hooks.rb:269 0.004
Given a computer 0.304
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.078
Then Tails is running from USB drive "old" 0.440
And all tps features are active 2.142
When I write some files expected to persist 2.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.355
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.301
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.340
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.415
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.881
And I log in to a new session 18.830
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.779
And I plug USB drive "to_upgrade" 2.495
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.402
Then the running Tails is installed on USB drive "to_upgrade" 19.563
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:326 1.928
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.429
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.862
Then all tps features from the old Tails version are active 1.670
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.262
And the expected persistent files created with the old Tails version are present in the filesystem 1.654
And all persistent directories from the old Tails version have safe access rights 2.445
After features/support/hooks.rb:326 0.610
After features/support/hooks.rb:100 0.007
6:32.237
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 12.511
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.004
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.077
And Tor is ready 24.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.650
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.577
Given I shutdown Tails and wait for the computer to power off 11.039
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.626
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# 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.391
When the network is plugged 0.077
And Tor is ready 17.333
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.473
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.949
Given I shutdown Tails and wait for the computer to power off 4.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.497
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.632
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.344
When the network is plugged 0.105
And Tor is ready 18.315
Then the Upgrader considers the system as up-to-date 0.373
# 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.346
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.469
After features/support/hooks.rb:326 0.795
After features/support/hooks.rb:100 0.019
36.272
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 11.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.929
But a current signing key is available on our website 0.000
When the network is plugged 0.579
And Tor is ready 17.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.207
After features/support/hooks.rb:326 1.305
After features/support/hooks.rb:100 0.000