Project Number Date
test_Tails_ISO_devel 3693 15 Feb 2025, 12:48

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:29.151 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:2.713
Before features/support/hooks.rb:269 0.004
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.837
When I start Tails from USB drive "old" with network unplugged 1:26.283
Then the boot device has safe access rights 3.227
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:326 3.573
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.641
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:33.724
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 31.812
And I take note of which tps features are available 1.382
Then a Tails persistence partition exists on USB drive "old" 0.865
And I shutdown Tails and wait for the computer to power off 8.286
After features/support/hooks.rb:326 0.225
After features/support/hooks.rb:100 0.011
Tags: @product
2:55.194
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.683
Then Tails is running from USB drive "old" 0.380
And all tps features are active 1.964
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 3.271
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 4.602
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.158
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.999
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.218
And I log in to a new session 19.092
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.654
And I plug USB drive "to_upgrade" 2.484
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.669
Then the running Tails is installed on USB drive "to_upgrade" 24.460
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 2.529
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.686
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.932
Then all tps features from the old Tails version are active 1.652
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.327
And the expected persistent files created with the old Tails version are present in the filesystem 1.433
And all persistent directories from the old Tails version have safe access rights 2.753
After features/support/hooks.rb:326 0.892
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:47.398
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 18.617
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.065
And Tor is ready 21.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.178
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.350
Given I shutdown Tails and wait for the computer to power off 8.916
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.735
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.515
And the file system changes introduced in version 6.2~testoverlayfs are present 0.451
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.339
# 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.396
When the network is plugged 0.066
And Tor is ready 19.639
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.738
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.156
Given I shutdown Tails and wait for the computer to power off 4.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.885
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.157
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.075
And Tor is ready 20.762
Then the Upgrader considers the system as up-to-date 0.321
# 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.064
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.154
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.518
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.212
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 21.256
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.475
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.000