Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 74 16 Oct 2024, 07:27

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:42.036 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:32.423
Before features/support/hooks.rb:269 0.014
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 29.449
When I start Tails from USB drive "old" with network unplugged 1:57.528
Then the boot device has safe access rights 3.138
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:326 3.959
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.233
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:22.962
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 32.806
And I take note of which tps features are available 1.600
Then a Tails persistence partition exists on USB drive "old" 0.854
And I shutdown Tails and wait for the computer to power off 8.465
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.292
Before features/support/hooks.rb:269 0.004
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.601
Then Tails is running from USB drive "old" 0.782
And all tps features are active 2.142
When I write some files expected to persist 1.951
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.339
And all persistence configuration files have safe access rights 0.595
And all persistent directories from the old Tails version have safe access rights 3.424
And I take note of which tps features are available 0.652
And I shutdown Tails and wait for the computer to power off 4.615
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.926
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.572
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 21.532
And I log in to a new session 20.453
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.807
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.410
Then the running Tails is installed on USB drive "to_upgrade" 27.306
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.359
After features/support/hooks.rb:326 3.951
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.110
Before features/support/hooks.rb:269 0.005
Given a computer 1.771
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.649
Then all tps features from the old Tails version are active 1.968
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.805
And the expected persistent files created with the old Tails version are present in the filesystem 1.841
And all persistent directories from the old Tails version have safe access rights 2.712
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:19.652
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.782
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.088
And Tor is ready 20.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.099
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.856
Given I shutdown Tails and wait for the computer to power off 10.882
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.462
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.215
And the file system changes introduced in version 6.2~testoverlayfs are present 0.420
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.379
# 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.309
When the network is plugged 0.075
And Tor is ready 19.775
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.227
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.641
Given I shutdown Tails and wait for the computer to power off 4.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.052
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.078
And Tor is ready 16.730
Then the Upgrader considers the system as up-to-date 0.363
# 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.248
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.159
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.750
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.002
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.784
But a current signing key is available on our website 0.000
When the network is plugged 0.131
And Tor is ready 22.042
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.316
After features/support/hooks.rb:326 0.642
After features/support/hooks.rb:100 0.000