Project Number Date
test_Tails_ISO_devel 3464 15 Jul 2024, 15:11

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 19:16.572 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:22.779
Before features/support/hooks.rb:269 0.007
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 32.225
When I start Tails from USB drive "old" with network unplugged 1:44.641
Then the boot device has safe access rights 3.372
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.156
And udev-watchdog is monitoring the correct device 0.381
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.521
After features/support/hooks.rb:100 0.011
Tags: @product
2:7.228
Before features/support/hooks.rb:269 0.007
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login 1:23.741
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 31.376
And I take note of which tps features are available 1.540
Then a Tails persistence partition exists on USB drive "old" 0.989
And I shutdown Tails and wait for the computer to power off 8.974
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.011
Tags: @product
2:50.598
Before features/support/hooks.rb:269 0.008
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.713
Then Tails is running from USB drive "old" 0.356
And all tps features are active 4.598
When I write some files expected to persist 1.877
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.327
And I take note of which tps features are available 0.523
And I shutdown Tails and wait for the computer to power off 4.390
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.894
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.024
Tags: @product
2:29.967
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 12.118
And I log in to a new session 17.903
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.816
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.087
Then the running Tails is installed on USB drive "to_upgrade" 21.128
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 2.331
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.427
Before features/support/hooks.rb:269 0.008
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.611
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.245
And the expected persistent files created with the old Tails version are present in the filesystem 1.505
And all persistent directories from the old Tails version have safe access rights 2.730
After features/support/hooks.rb:326 0.639
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:33.286
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.751
And no SquashFS delta is installed 0.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.499
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.378
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.065
And Tor is ready 21.604
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.318
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.603
Given I shutdown Tails and wait for the computer to power off 13.170
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.139
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
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.352
# 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.360
When the network is plugged 0.047
And Tor is ready 19.386
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.692
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.018
Given I shutdown Tails and wait for the computer to power off 4.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.830
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.129
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.049
And Tor is ready 18.616
Then the Upgrader considers the system as up-to-date 0.389
# 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.671
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.069
After features/support/hooks.rb:326 0.848
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
37.285
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.390
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.703
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.937
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 20.062
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.079
After features/support/hooks.rb:326 0.679
After features/support/hooks.rb:100 0.000