Project Number Date
test_Tails_ISO_stable 4798 18 Apr 2024, 21:18

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 18:16.287 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
1:47.579
Before features/support/hooks.rb:259 0.007
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 23.089
When I start Tails from USB drive "old" with network unplugged 1:19.034
Then the boot device has safe access rights 3.072
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.130
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:305 6.841
After features/support/hooks.rb:89 0.010
Tags: @product
2:3.770
Before features/support/hooks.rb:259 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:18.003
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 34.036
And I take note of which tps features are available 1.476
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.929
After features/support/hooks.rb:305 0.160
After features/support/hooks.rb:89 0.011
Tags: @product
2:32.829
Before features/support/hooks.rb:259 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.138
Then Tails is running from USB drive "old" 0.414
And all tps features are active 2.175
When I write some files expected to persist 1.830
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.309
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.654
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 4.770
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.362
After features/support/hooks.rb:305 0.132
After features/support/hooks.rb:89 0.010
Tags: @product
2:25.197
Before features/support/hooks.rb:259 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.633
And I log in to a new session 20.263
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.435
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.302
Then the running Tails is installed on USB drive "to_upgrade" 16.727
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:305 1.621
After features/support/hooks.rb:89 0.000
Tags: @product
2:13.985
Before features/support/hooks.rb:259 0.005
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.458
Then all tps features from the old Tails version are active 1.746
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.362
And the expected persistent files created with the old Tails version are present in the filesystem 1.438
And all persistent directories from the old Tails version have safe access rights 2.478
After features/support/hooks.rb:305 1.080
After features/support/hooks.rb:89 0.010
6:33.922
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.207
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
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.440
When the network is plugged 0.041
And Tor is ready 19.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.525
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.439
Given I shutdown Tails and wait for the computer to power off 6.739
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.051
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.597
And the file system changes introduced in version 6.2~testoverlayfs are present 0.374
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.306
When the network is plugged 0.053
And Tor is ready 18.206
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.726
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.500
Given I shutdown Tails and wait for the computer to power off 4.238
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.220
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.174
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.033
And Tor is ready 16.481
Then the Upgrader considers the system as up-to-date 0.345
# 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.297
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.087
After features/support/hooks.rb:305 0.704
After features/support/hooks.rb:89 0.018
39.003
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.792
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
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.492
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 20.082
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.103
After features/support/hooks.rb:305 0.720
After features/support/hooks.rb:89 0.000