Project Number Date
test_Tails_ISO_devel 3645 12 Jan 2025, 17:35

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:40.642 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:15.003
Before features/support/hooks.rb:269 0.003
Given a computer 0.151
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 30.767
When I start Tails from USB drive "old" with network unplugged 1:38.871
Then the boot device has safe access rights 3.059
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.248
After features/support/hooks.rb:326 7.503
After features/support/hooks.rb:100 0.006
Tags: @product
2:0.508
Before features/support/hooks.rb:269 0.003
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 1:20.223
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 31.322
And I take note of which tps features are available 1.432
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 6.172
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.006
Tags: @product
2:57.053
Before features/support/hooks.rb:269 0.002
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.454
Then Tails is running from USB drive "old" 0.282
And all tps features are active 1.892
When I write some files expected to persist 1.744
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.343
And all persistent directories from the old Tails version have safe access rights 2.685
And I take note of which tps features are available 0.534
And I shutdown Tails and wait for the computer to power off 4.579
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.105
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.006
Tags: @product
2:30.674
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.967
And I log in to a new session 20.335
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.747
And I plug USB drive "to_upgrade" 2.353
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.312
Then the running Tails is installed on USB drive "to_upgrade" 21.545
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 2.236
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.841
Before features/support/hooks.rb:269 0.002
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.924
Then all tps features from the old Tails version are active 1.595
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.278
And the expected persistent files created with the old Tails version are present in the filesystem 1.338
And all persistent directories from the old Tails version have safe access rights 2.236
After features/support/hooks.rb:326 0.803
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:9.592
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 12.216
And no SquashFS delta is installed 0.242
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.081
And Tor is ready 24.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.576
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.626
Given I shutdown Tails and wait for the computer to power off 8.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.305
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.293
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.070
And Tor is ready 18.170
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.483
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.007
Given I shutdown Tails and wait for the computer to power off 4.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.515
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.074
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.072
And Tor is ready 19.453
Then the Upgrader considers the system as up-to-date 0.297
# 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 16.165
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.174
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
38.969
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 11.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 20.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.532
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.000