Project Number Date
test_Tails_ISO_devel 3904 09 Jul 2025, 14: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 26:1.623 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:59.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 40.192
When I start Tails from USB drive "old" with network unplugged 2:12.199
Then the boot device has safe access rights 5.112
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.367
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 7.489
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.286
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 1.498
And I start Tails from USB drive "old" with network unplugged and I login 1:55.803
Then Tails is running from USB drive "old" 0.528
And I create a persistent partition 42.100
And I take note of which tps features are available 3.759
Then a Tails persistence partition exists on USB drive "old" 2.280
And I shutdown Tails and wait for the computer to power off 8.316
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.009
Tags: @product
4:0.211
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:4.375
Then Tails is running from USB drive "old" 0.397
And all tps features are active 5.444
When I write some files expected to persist 3.526
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.477
And all persistence configuration files have safe access rights 0.871
And all persistent directories from the old Tails version have safe access rights 3.231
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.776
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 36.427
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.009
Tags: @product
3:18.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 17.153
And I log in to a new session 24.827
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.628
And I plug USB drive "to_upgrade" 4.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.067
Then the running Tails is installed on USB drive "to_upgrade" 36.186
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:330 1.011
After features/support/hooks.rb:100 0.000
Tags: @product
3:3.132
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:48.066
Then all tps features from the old Tails version are active 4.748
And Tails is running from USB drive "to_upgrade" 0.629
And the boot device has safe access rights 4.416
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 3.386
After features/support/hooks.rb:330 1.081
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:52.999
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.673
And no SquashFS delta is installed 0.260
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.734
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.471
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.530
When the network is plugged 0.084
And Tor is ready 32.332
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.800
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.992
Given I shutdown Tails and wait for the computer to power off 14.505
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:39.038
Then Tails is running version 6.2~testoverlayfs 0.330
And all tps features are active 2.779
And the file system changes introduced in version 6.2~testoverlayfs are present 0.363
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.355
When the network is plugged 0.080
And Tor is ready 29.652
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.753
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.562
Given I shutdown Tails and wait for the computer to power off 6.724
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:32.443
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 3.251
And the file system changes introduced in version 6.3~testoverlayfs are present 0.767
And only the 6.3~testoverlayfs SquashFS delta is installed 0.139
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.071
And Tor is ready 35.228
Then the Upgrader considers the system as up-to-date 0.507
# 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 22.388
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.978
After features/support/hooks.rb:330 0.903
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
52.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.288
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.132
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 23.797
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.601
After features/support/hooks.rb:330 1.482
After features/support/hooks.rb:100 0.000