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

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:34.184 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.128
Before features/support/hooks.rb:269 0.008
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 30.837
When I start Tails from USB drive "old" with network unplugged 1:27.490
Then the boot device has safe access rights 3.390
And Tails is running from USB drive "old" 0.377
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 3.774
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.870
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:21.491
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 31.392
And I take note of which tps features are available 1.964
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 8.588
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.011
Tags: @product
2:50.645
Before features/support/hooks.rb:269 0.008
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.342
Then Tails is running from USB drive "old" 1.416
And all tps features are active 2.408
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 3.620
And I take note of which tps features are available 0.535
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" 25.331
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.000
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.901
And I log in to a new session 22.621
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.759
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.321
Then the running Tails is installed on USB drive "to_upgrade" 22.539
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 3.667
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.842
Before features/support/hooks.rb:269 0.012
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.959
Then all tps features from the old Tails version are active 1.903
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.262
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.601
After features/support/hooks.rb:326 1.185
After features/support/hooks.rb:100 0.013
6:43.682
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.909
And no SquashFS delta is installed 0.511
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.595
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.545
When the network is plugged 0.174
And Tor is ready 18.244
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.943
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.741
Given I shutdown Tails and wait for the computer to power off 8.955
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.070
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 3.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.276
When the network is plugged 0.088
And Tor is ready 17.978
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.187
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.924
Given I shutdown Tails and wait for the computer to power off 4.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.287
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.868
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.352
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.100
And Tor is ready 19.387
Then the Upgrader considers the system as up-to-date 0.375
# 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.936
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.348
After features/support/hooks.rb:326 0.784
After features/support/hooks.rb:100 0.024
40.014
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 12.810
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.765
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 1.468
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 17.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.135
After features/support/hooks.rb:326 0.901
After features/support/hooks.rb:100 0.000