Project Number Date
test_Tails_ISO_devel 3678 03 Feb 2025, 17:50

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 18:41.577 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:4.367
Before features/support/hooks.rb:269 0.003
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 28.906
When I start Tails from USB drive "old" with network unplugged 1:30.075
Then the boot device has safe access rights 2.952
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.378
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 3.767
After features/support/hooks.rb:100 0.005
Tags: @product
2:3.741
Before features/support/hooks.rb:269 0.002
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:24.465
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 29.933
And I take note of which tps features are available 1.483
Then a Tails persistence partition exists on USB drive "old" 0.787
And I shutdown Tails and wait for the computer to power off 6.559
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.006
Tags: @product
2:49.045
Before features/support/hooks.rb:269 0.002
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.607
Then Tails is running from USB drive "old" 1.404
And all tps features are active 2.367
When I write some files expected to persist 3.106
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.558
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.285
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.532
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.006
Tags: @product
2:31.971
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.547
And I log in to a new session 18.668
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.675
And I plug USB drive "to_upgrade" 2.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.091
Then the running Tails is installed on USB drive "to_upgrade" 24.209
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 3.802
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.507
Before features/support/hooks.rb:269 0.003
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.801
Then all tps features from the old Tails version are active 1.699
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.524
And the expected persistent files created with the old Tails version are present in the filesystem 1.679
And all persistent directories from the old Tails version have safe access rights 2.321
After features/support/hooks.rb:326 0.884
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:21.829
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.099
And no SquashFS delta is installed 0.738
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.654
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.075
And Tor is ready 24.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.207
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.227
Given I shutdown Tails and wait for the computer to power off 8.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.146
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.424
And the file system changes introduced in version 6.2~testoverlayfs are present 0.407
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.262
When the network is plugged 0.087
And Tor is ready 17.757
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.595
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.957
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.540
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.196
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.091
And Tor is ready 21.971
Then the Upgrader considers the system as up-to-date 0.328
# 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.036
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.908
After features/support/hooks.rb:326 0.837
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
38.114
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.867
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.660
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.123
And Tor is ready 22.460
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.888
After features/support/hooks.rb:326 1.076
After features/support/hooks.rb:100 0.000