Project Number Date
test_Tails_ISO_stable 4984 31 Jul 2024, 08:51

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:4.377 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:25.546
Before features/support/hooks.rb:269 0.010
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 33.452
When I start Tails from USB drive "old" with network unplugged 1:46.569
Then the boot device has safe access rights 3.121
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.826
After features/support/hooks.rb:100 0.014
Tags: @product
2:29.723
Before features/support/hooks.rb:269 0.010
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:42.931
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 34.799
And I take note of which tps features are available 1.681
Then a Tails persistence partition exists on USB drive "old" 0.916
And I shutdown Tails and wait for the computer to power off 8.789
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.523
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.113
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.117
When I write some files expected to persist 1.798
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.486
And all persistent directories from the old Tails version have safe access rights 2.709
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.753
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.143
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.013
Tags: @product
2:29.949
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.984
And I log in to a new session 21.143
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.543
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.582
Then the running Tails is installed on USB drive "to_upgrade" 17.777
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 3.353
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.882
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.050
Then all tps features from the old Tails version are active 1.701
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.534
And all persistent directories from the old Tails version have safe access rights 2.667
After features/support/hooks.rb:326 1.048
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:36.623
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.821
And no SquashFS delta is installed 0.251
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.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.748
And Tor is ready 19.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.376
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.976
Given I shutdown Tails and wait for the computer to power off 8.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.494
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.183
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
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.305
# 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.333
When the network is plugged 0.059
And Tor is ready 46.836
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.670
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.728
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.395
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.096
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.044
And Tor is ready 18.985
Then the Upgrader considers the system as up-to-date 0.312
# 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 13.967
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.967
After features/support/hooks.rb:326 0.879
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
37.127
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.967
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 1.704
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 18.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.787
After features/support/hooks.rb:326 1.022
After features/support/hooks.rb:100 0.000