Project Number Date
test_Tails_ISO_devel 3654 19 Jan 2025, 17:37

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 20:17.104 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:8.874
Before features/support/hooks.rb:269 0.002
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.087
When I start Tails from USB drive "old" with network unplugged 1:32.642
Then the boot device has safe access rights 2.893
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 3.743
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.869
Before features/support/hooks.rb:269 0.003
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:26.177
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 30.856
And I take note of which tps features are available 1.398
Then a Tails persistence partition exists on USB drive "old" 0.758
And I shutdown Tails and wait for the computer to power off 8.182
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.006
Tags: @product
2:50.851
Before features/support/hooks.rb:269 0.002
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.578
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.045
When I write some files expected to persist 1.933
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.365
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.328
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.054
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.006
Tags: @product
2:28.088
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 12.191
And I log in to a new session 19.635
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.622
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.303
Then the running Tails is installed on USB drive "to_upgrade" 19.535
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:326 2.315
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.341
Before features/support/hooks.rb:269 0.003
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.245
Then all tps features from the old Tails version are active 1.604
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 3.384
And the expected persistent files created with the old Tails version are present in the filesystem 1.349
And all persistent directories from the old Tails version have safe access rights 2.277
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
7:41.295
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.250
And no SquashFS delta is installed 0.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.086
And Tor is ready 19.588
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.531
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.272
Given I shutdown Tails and wait for the computer to power off 1:12.317
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.910
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.346
When the network is plugged 0.062
And Tor is ready 19.759
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.221
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.788
Given I shutdown Tails and wait for the computer to power off 4.170
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.510
Then Tails is running version 6.3~testoverlayfs 0.033
And all tps features are active 2.094
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.065
And Tor is ready 17.981
Then the Upgrader considers the system as up-to-date 10.786
# 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.014
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.988
After features/support/hooks.rb:326 0.739
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
35.784
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.930
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.670
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 18.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.238
After features/support/hooks.rb:326 0.702
After features/support/hooks.rb:100 0.000