Project Number Date
test_Tails_ISO_stable 5409 21 Jan 2025, 18:24

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 20:40.575 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:9.624
Before features/support/hooks.rb:269 0.007
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.246
When I start Tails from USB drive "old" with network unplugged 1:32.230
Then the boot device has safe access rights 3.656
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:326 7.791
After features/support/hooks.rb:100 0.013
Tags: @product
2:33.115
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:41.511
Then Tails is running from USB drive "old" 0.487
And I create a persistent partition 38.519
And I take note of which tps features are available 2.359
Then a Tails persistence partition exists on USB drive "old" 1.041
And I shutdown Tails and wait for the computer to power off 8.962
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.011
Tags: @product
2:58.623
Before features/support/hooks.rb:269 0.009
Given a computer 0.297
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.998
Then Tails is running from USB drive "old" 0.607
And all tps features are active 2.072
When I write some files expected to persist 2.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.354
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.781
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.885
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.971
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.578
And I log in to a new session 20.193
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.581
And I plug USB drive "to_upgrade" 2.692
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.333
Then the running Tails is installed on USB drive "to_upgrade" 26.137
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:326 6.932
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.677
Before features/support/hooks.rb:269 0.006
Given a computer 0.262
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.683
Then all tps features from the old Tails version are active 1.603
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.493
And the expected persistent files created with the old Tails version are present in the filesystem 1.573
And all persistent directories from the old Tails version have safe access rights 2.715
After features/support/hooks.rb:326 0.900
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:18.817
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 11.181
And no SquashFS delta is installed 0.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.081
And Tor is ready 21.316
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.710
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.428
Given I shutdown Tails and wait for the computer to power off 8.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.143
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.350
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.359
When the network is plugged 0.092
And Tor is ready 47.653
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.694
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.637
Given I shutdown Tails and wait for the computer to power off 6.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.363
Then Tails is running version 6.3~testoverlayfs 0.035
And all tps features are active 3.911
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.405
When the network is plugged 0.081
And Tor is ready 20.900
Then the Upgrader considers the system as up-to-date 0.377
# 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 16.452
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.666
After features/support/hooks.rb:326 0.902
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
36.744
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 10.857
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.584
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.015
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.000