Project Number Date
test_Tails_ISO_stable 4764 03 Apr 2024, 12:01

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 17:36.340 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:45.444
Before features/support/hooks.rb:245 0.008
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 26.042
When I start Tails from USB drive "old" with network unplugged 1:14.085
Then the boot device has safe access rights 3.040
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 6.839
After features/support/hooks.rb:75 0.009
Tags: @product
2:13.517
Before features/support/hooks.rb:245 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:19.799
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 37.141
And I take note of which tps features are available 1.370
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 13.742
After features/support/hooks.rb:291 0.205
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.220
Before features/support/hooks.rb:245 0.007
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.832
Then Tails is running from USB drive "old" 0.443
And all tps features are active 2.115
When I write some files expected to persist 1.730
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 3.092
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 4.239
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.421
After features/support/hooks.rb:291 0.118
After features/support/hooks.rb:75 0.011
Tags: @product
2:19.357
Before features/support/hooks.rb:245 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 9.747
And I log in to a new session 16.530
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.286
And I plug USB drive "to_upgrade" 2.378
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.637
Then the running Tails is installed on USB drive "to_upgrade" 15.388
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:291 3.584
After features/support/hooks.rb:75 0.000
Tags: @product
2:2.583
Before features/support/hooks.rb:245 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.254
Then all tps features from the old Tails version are active 1.466
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.007
And the expected persistent files created with the old Tails version are present in the filesystem 1.516
And all persistent directories from the old Tails version have safe access rights 2.821
After features/support/hooks.rb:291 0.870
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:7.856
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.682
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.062
And Tor is ready 21.025
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.074
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.724
Given I shutdown Tails and wait for the computer to power off 6.488
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.244
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.111
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.409
# 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.124
And Tor is ready 19.715
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.341
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.017
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.201
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.110
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.063
And Tor is ready 15.609
Then the Upgrader considers the system as up-to-date 0.286
# 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.191
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.840
After features/support/hooks.rb:291 0.667
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
31.359
Before features/support/hooks.rb:245 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.288
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.489
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 16.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.972
After features/support/hooks.rb:291 0.868
After features/support/hooks.rb:75 0.000