Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 42 26 Aug 2024, 16:35

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:26.908 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:10.381
Before features/support/hooks.rb:269 0.007
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.654
When I start Tails from USB drive "old" with network unplugged 1:31.408
Then the boot device has safe access rights 3.068
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.562
After features/support/hooks.rb:100 0.011
Tags: @product
2:15.610
Before features/support/hooks.rb:269 0.008
Given a computer 0.320
And I start Tails from USB drive "old" with network unplugged and I login 1:32.635
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 30.787
And I take note of which tps features are available 2.023
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 8.613
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.011
Tags: @product
2:56.043
Before features/support/hooks.rb:269 0.008
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.199
Then Tails is running from USB drive "old" 0.946
And all tps features are active 2.238
When I write some files expected to persist 1.973
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.304
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.429
And I take note of which tps features are available 0.415
And I shutdown Tails and wait for the computer to power off 4.401
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.479
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.014
Tags: @product
2:35.267
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 12.856
And I log in to a new session 21.337
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.976
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.406
Then the running Tails is installed on USB drive "to_upgrade" 18.775
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.117
Before features/support/hooks.rb:269 0.007
Given a computer 0.246
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.057
Then all tps features from the old Tails version are active 1.766
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.696
And the expected persistent files created with the old Tails version are present in the filesystem 1.403
And all persistent directories from the old Tails version have safe access rights 2.597
After features/support/hooks.rb:326 0.822
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:34.373
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 13.229
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.104
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.179
And Tor is ready 21.127
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.848
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.295
Given I shutdown Tails and wait for the computer to power off 10.753
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.956
Then Tails is running version 6.2~testoverlayfs 0.055
And all tps features are active 2.254
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.281
When the network is plugged 0.068
And Tor is ready 15.941
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.127
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.714
Given I shutdown Tails and wait for the computer to power off 4.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.267
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.100
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.395
When the network is plugged 0.065
And Tor is ready 19.193
Then the Upgrader considers the system as up-to-date 0.331
# 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 13.609
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.255
After features/support/hooks.rb:326 0.782
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
39.114
Before features/support/hooks.rb:269 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.526
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
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.062
And Tor is ready 18.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.611
After features/support/hooks.rb:326 1.125
After features/support/hooks.rb:100 0.000