Project Number Date
test_Tails_ISO_stable 4952 17 Jul 2024, 13:02

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:9.407 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:16.532
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.253
When I start Tails from USB drive "old" with network unplugged 1:39.510
Then the boot device has safe access rights 3.400
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.365
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 7.274
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.900
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:23.122
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 32.401
And I take note of which tps features are available 1.511
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 8.492
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.947
Before features/support/hooks.rb:269 0.005
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.764
Then Tails is running from USB drive "old" 0.354
And all tps features are active 2.167
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.635
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.457
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.389
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.719
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 10.669
And I log in to a new session 19.665
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.984
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.189
Then the running Tails is installed on USB drive "to_upgrade" 23.331
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:326 3.753
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.382
Before features/support/hooks.rb:269 0.004
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.239
Then all tps features from the old Tails version are active 1.553
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.077
And the expected persistent files created with the old Tails version are present in the filesystem 1.629
And all persistent directories from the old Tails version have safe access rights 2.380
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:28.430
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.503
And no SquashFS delta is installed 0.534
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.552
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.039
And Tor is ready 21.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.927
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.081
Given I shutdown Tails and wait for the computer to power off 1:15.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.631
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.303
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.272
When the network is plugged 0.049
And Tor is ready 17.174
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.768
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.645
Given I shutdown Tails and wait for the computer to power off 4.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.167
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.490
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.387
When the network is plugged 0.073
And Tor is ready 19.099
Then the Upgrader considers the system as up-to-date 0.357
# 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.111
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.003
After features/support/hooks.rb:326 0.809
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
38.493
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 1.131
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 20.629
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.127
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.000