Project Number Date
test_Tails_ISO_stable 5432 30 Jan 2025, 08:43

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:51.368 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
1:58.539
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 27.477
When I start Tails from USB drive "old" with network unplugged 1:25.696
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.563
After features/support/hooks.rb:100 0.008
Tags: @product
1:59.751
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:19.236
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 31.460
And I take note of which tps features are available 1.482
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 6.269
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:43.476
Before features/support/hooks.rb:269 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.747
Then Tails is running from USB drive "old" 0.864
And all tps features are active 1.903
When I write some files expected to persist 1.630
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.530
And all persistent directories from the old Tails version have safe access rights 2.498
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.201
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.158
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.366
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 10.341
And I log in to a new session 18.364
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.609
And I plug USB drive "to_upgrade" 2.515
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.500
Then the running Tails is installed on USB drive "to_upgrade" 20.624
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 6.798
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.344
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.104
Then all tps features from the old Tails version are active 1.618
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.381
And the expected persistent files created with the old Tails version are present in the filesystem 1.391
And all persistent directories from the old Tails version have safe access rights 2.329
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
7:45.176
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.039
And no SquashFS delta is installed 0.607
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
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.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.285
When the network is plugged 0.076
And Tor is ready 21.656
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.547
Given I shutdown Tails and wait for the computer to power off 1:20.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.197
Then Tails is running version 6.2~testoverlayfs 0.038
And all tps features are active 2.268
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.131
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.258
When the network is plugged 0.081
And Tor is ready 19.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.864
Given I shutdown Tails and wait for the computer to power off 4.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.940
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.946
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.388
When the network is plugged 0.064
And Tor is ready 18.252
Then the Upgrader considers the system as up-to-date 0.411
# 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.874
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.146
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.714
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 13.699
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.707
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 19.280
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.780
After features/support/hooks.rb:326 2.039
After features/support/hooks.rb:100 0.000