Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 23 10 Aug 2024, 06:43

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:39.680 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:15.542
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 29.758
When I start Tails from USB drive "old" with network unplugged 1:40.246
Then the boot device has safe access rights 3.191
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 7.392
After features/support/hooks.rb:100 0.013
Tags: @product
2:8.846
Before features/support/hooks.rb:269 0.011
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login 1:24.499
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 32.153
And I take note of which tps features are available 1.501
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 9.238
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.681
Before features/support/hooks.rb:269 0.006
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.200
Then Tails is running from USB drive "old" 1.115
And all tps features are active 2.107
When I write some files expected to persist 3.321
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 2.594
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 4.097
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.807
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.094
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 12.762
And I log in to a new session 23.631
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.491
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.386
Then the running Tails is installed on USB drive "to_upgrade" 18.870
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.409
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.085
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.182
Then all tps features from the old Tails version are active 1.569
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.673
And the expected persistent files created with the old Tails version are present in the filesystem 1.530
And all persistent directories from the old Tails version have safe access rights 2.587
After features/support/hooks.rb:326 1.141
After features/support/hooks.rb:100 0.011
6:45.976
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.136
And no SquashFS delta is installed 0.185
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.083
And Tor is ready 24.312
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.392
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.959
Given I shutdown Tails and wait for the computer to power off 10.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.889
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.384
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.328
When the network is plugged 0.092
And Tor is ready 18.091
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.802
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.311
Given I shutdown Tails and wait for the computer to power off 6.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.236
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.386
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.095
And Tor is ready 18.746
Then the Upgrader considers the system as up-to-date 0.378
# 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.487
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.101
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.024
39.453
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.500
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 0.901
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 21.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.373
After features/support/hooks.rb:326 1.522
After features/support/hooks.rb:100 0.000