Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 22 09 Aug 2024, 16:24

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:22.353 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
1:57.457
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.697
When I start Tails from USB drive "old" with network unplugged 1:23.700
Then the boot device has safe access rights 2.793
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 6.978
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.559
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:21.996
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 32.439
And I take note of which tps features are available 1.462
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.339
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.133
Before features/support/hooks.rb:269 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.748
Then Tails is running from USB drive "old" 0.633
And all tps features are active 1.979
When I write some files expected to persist 1.689
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
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.457
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.121
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.018
Tags: @product
2:24.717
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.777
And I log in to a new session 19.316
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.387
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.200
Then the running Tails is installed on USB drive "to_upgrade" 17.145
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 2.672
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.556
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.174
Then all tps features from the old Tails version are active 1.727
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.353
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.323
After features/support/hooks.rb:326 0.830
After features/support/hooks.rb:100 0.008
6:13.473
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 13.208
And no SquashFS delta is installed 0.481
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.993
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.061
And Tor is ready 21.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.457
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.643
Given I shutdown Tails and wait for the computer to power off 8.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.860
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 2.055
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.264
When the network is plugged 0.086
And Tor is ready 18.976
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.719
Given I shutdown Tails and wait for the computer to power off 4.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.434
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.021
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.078
# 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.419
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.072
And Tor is ready 18.904
Then the Upgrader considers the system as up-to-date 0.346
# 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 14.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.155
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.019
34.457
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.730
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.420
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 16.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.944
After features/support/hooks.rb:326 2.278
After features/support/hooks.rb:100 0.000