Project Number Date
test_Tails_ISO_devel 3482 16 Aug 2024, 12:57

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 21:49.476 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:6.875
Before features/support/hooks.rb:269 0.009
Given a computer 0.264
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 29.721
When I start Tails from USB drive "old" with network unplugged 1:31.313
Then the boot device has safe access rights 3.330
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.382
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 3.562
After features/support/hooks.rb:100 0.014
Tags: @product
2:5.877
Before features/support/hooks.rb:269 0.009
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:22.538
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 31.917
And I take note of which tps features are available 1.526
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.543
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.807
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.965
Then Tails is running from USB drive "old" 0.344
And all tps features are active 2.067
When I write some files expected to persist 1.848
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.874
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 4.490
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.925
After features/support/hooks.rb:326 0.116
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.498
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 11.755
And I log in to a new session 18.097
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.959
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.648
Then the running Tails is installed on USB drive "to_upgrade" 21.154
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 3.228
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.193
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.209
Then all tps features from the old Tails version are active 1.722
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.618
And the expected persistent files created with the old Tails version are present in the filesystem 1.574
And all persistent directories from the old Tails version have safe access rights 2.553
After features/support/hooks.rb:326 0.669
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
9:12.893
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 14.452
And no SquashFS delta is installed 0.254
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.379
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.609
When the network is plugged 0.072
And Tor is ready 20.796
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.326
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.337
Given I shutdown Tails and wait for the computer to power off 1:25.610
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.949
Then Tails is running version 6.2~testoverlayfs 0.032
And all tps features are active 2.627
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.377
# 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.320
When the network is plugged 0.084
And Tor is ready 17.990
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.546
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.491
Given I shutdown Tails and wait for the computer to power off 1:8.797
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.978
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.729
And the file system changes introduced in version 6.3~testoverlayfs are present 0.637
And only the 6.3~testoverlayfs SquashFS delta is installed 0.110
# 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.455
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.318
When the network is plugged 0.093
And Tor is ready 16.542
Then the Upgrader considers the system as up-to-date 10.955
# 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.289
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.949
After features/support/hooks.rb:326 0.844
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
42.330
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 17.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 0.816
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 18.301
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.523
After features/support/hooks.rb:326 0.683
After features/support/hooks.rb:100 0.000