Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 31 03 Apr 2025, 09:36

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:33.499 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:6.853
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.746
When I start Tails from USB drive "old" with network unplugged 1:31.911
Then the boot device has safe access rights 2.991
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 3.539
After features/support/hooks.rb:100 0.006
Tags: @product
2:6.251
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:22.793
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 32.399
And I take note of which tps features are available 1.478
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.282
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.006
Tags: @product
2:56.178
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.263
Then Tails is running from USB drive "old" 0.319
And all tps features are active 1.850
When I write some files expected to persist 1.802
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.355
And all persistent directories from the old Tails version have safe access rights 2.444
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 4.358
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.909
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.006
Tags: @product
2:30.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 8.668
And I log in to a new session 18.222
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.507
And I plug USB drive "to_upgrade" 2.407
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.350
Then the running Tails is installed on USB drive "to_upgrade" 25.543
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 6.623
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.668
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.928
Then all tps features from the old Tails version are active 1.870
And Tails is running from USB drive "to_upgrade" 0.426
And the boot device has safe access rights 3.732
And the expected persistent files created with the old Tails version are present in the filesystem 1.637
And all persistent directories from the old Tails version have safe access rights 2.887
After features/support/hooks.rb:330 1.694
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
6:51.165
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.224
And no SquashFS delta is installed 0.256
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.576
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.557
When the network is plugged 0.084
And Tor is ready 23.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.191
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.639
Given I shutdown Tails and wait for the computer to power off 8.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.313
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.122
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.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.406
# 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.284
When the network is plugged 0.069
And Tor is ready 20.914
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.511
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.845
Given I shutdown Tails and wait for the computer to power off 4.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.123
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.044
And the file system changes introduced in version 6.3~testoverlayfs are present 0.702
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.372
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.339
When the network is plugged 0.066
And Tor is ready 19.032
Then the Upgrader considers the system as up-to-date 0.280
# 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.637
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.921
After features/support/hooks.rb:330 0.690
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
38.232
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.354
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.155
And Tor is ready 20.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.794
After features/support/hooks.rb:330 0.689
After features/support/hooks.rb:100 0.000