Project Number Date
test_Tails_ISO_devel 3664 27 Jan 2025, 20:57

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:55.827 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:10.623
Before features/support/hooks.rb:269 0.002
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 33.323
When I start Tails from USB drive "old" with network unplugged 1:31.391
Then the boot device has safe access rights 3.468
And Tails is running from USB drive "old" 0.413
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.130
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.711
Before features/support/hooks.rb:269 0.003
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:27.782
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 34.177
And I take note of which tps features are available 1.845
Then a Tails persistence partition exists on USB drive "old" 0.905
And I shutdown Tails and wait for the computer to power off 8.365
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.005
Tags: @product
3:10.245
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:29.209
Then Tails is running from USB drive "old" 0.406
And all tps features are active 2.244
When I write some files expected to persist 1.846
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.837
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.540
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.840
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.007
Tags: @product
2:44.151
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 13.327
And I log in to a new session 23.051
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.347
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.691
Then the running Tails is installed on USB drive "to_upgrade" 24.872
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:326 2.823
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.089
Before features/support/hooks.rb:269 0.002
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.067
Then all tps features from the old Tails version are active 1.879
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 3.392
And the expected persistent files created with the old Tails version are present in the filesystem 1.745
And all persistent directories from the old Tails version have safe access rights 2.521
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:37.459
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 15.356
And no SquashFS delta is installed 0.356
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.602
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.075
And Tor is ready 26.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.535
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.242
Given I shutdown Tails and wait for the computer to power off 11.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.443
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.456
And the file system changes introduced in version 6.2~testoverlayfs are present 0.395
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.483
# 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.356
When the network is plugged 0.073
And Tor is ready 18.498
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.639
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.195
Given I shutdown Tails and wait for the computer to power off 4.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.032
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.080
And Tor is ready 20.032
Then the Upgrader considers the system as up-to-date 0.331
# 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.448
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.990
After features/support/hooks.rb:326 0.732
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
39.545
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 10.675
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.107
But a current signing key is available on our website 0.000
When the network is plugged 0.203
And Tor is ready 22.341
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.652
After features/support/hooks.rb:326 0.900
After features/support/hooks.rb:100 0.000