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

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:23.198 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:27.110
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 44.777
When I start Tails from USB drive "old" with network unplugged 1:36.881
Then the boot device has safe access rights 3.117
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 3.603
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.725
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:27.755
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 32.539
And I take note of which tps features are available 1.635
Then a Tails persistence partition exists on USB drive "old" 0.923
And I shutdown Tails and wait for the computer to power off 8.256
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.507
Before features/support/hooks.rb:269 0.004
Given a computer 0.285
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.805
Then Tails is running from USB drive "old" 1.205
And all tps features are active 2.303
When I write some files expected to persist 2.418
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.583
And I take note of which tps features are available 0.563
And I shutdown Tails and wait for the computer to power off 4.185
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.443
After features/support/hooks.rb:326 0.086
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.785
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.747
And I log in to a new session 22.244
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.292
And I plug USB drive "to_upgrade" 2.574
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.698
Then the running Tails is installed on USB drive "to_upgrade" 18.749
And I unplug USB drive "to_upgrade" 0.261
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.717
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.286
Before features/support/hooks.rb:269 0.006
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.688
Then all tps features from the old Tails version are active 1.634
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.335
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.558
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:21.316
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.667
And no SquashFS delta is installed 0.406
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.065
And Tor is ready 27.370
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.519
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.457
Given I shutdown Tails and wait for the computer to power off 10.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.610
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.221
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.286
When the network is plugged 0.076
And Tor is ready 17.868
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.852
Given I shutdown Tails and wait for the computer to power off 4.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.570
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.125
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.067
And Tor is ready 15.621
Then the Upgrader considers the system as up-to-date 0.323
# 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.041
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.037
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.465
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 11.011
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.174
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 1.042
But a current signing key is available on our website 0.000
When the network is plugged 0.123
And Tor is ready 19.602
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.449
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.000