Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 92 30 Jan 2025, 21:04

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:38.468 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:4.523
Before features/support/hooks.rb:269 0.004
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 30.360
When I start Tails from USB drive "old" with network unplugged 1:28.242
Then the boot device has safe access rights 3.416
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.261
After features/support/hooks.rb:326 3.625
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.709
Before features/support/hooks.rb:269 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:33.132
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 32.747
And I take note of which tps features are available 1.786
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.652
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.007
Tags: @product
3:2.200
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.640
Then Tails is running from USB drive "old" 1.377
And all tps features are active 2.354
When I write some files expected to persist 2.095
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 1.397
And all persistent directories from the old Tails version have safe access rights 2.702
And I take note of which tps features are available 0.563
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.288
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.684
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.420
And I log in to a new session 20.937
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.735
And I plug USB drive "to_upgrade" 2.509
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.965
Then the running Tails is installed on USB drive "to_upgrade" 18.665
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 3.579
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.136
Before features/support/hooks.rb:269 0.005
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.768
Then all tps features from the old Tails version are active 1.792
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.861
And the expected persistent files created with the old Tails version are present in the filesystem 1.595
And all persistent directories from the old Tails version have safe access rights 2.564
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:49.461
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.698
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.686
When the network is plugged 0.071
And Tor is ready 18.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.882
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.076
Given I shutdown Tails and wait for the computer to power off 8.738
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.546
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.516
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.427
# 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.308
When the network is plugged 0.065
And Tor is ready 18.060
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.365
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.379
Given I shutdown Tails and wait for the computer to power off 4.738
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.194
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.675
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.078
And Tor is ready 15.672
Then the Upgrader considers the system as up-to-date 0.320
# 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.319
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.058
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
34.752
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 9.974
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 16.551
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.652
After features/support/hooks.rb:326 0.834
After features/support/hooks.rb:100 0.000