Project Number Date
test_Tails_ISO_20522-ocr-more 36 21 Jan 2025, 05:19

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 18:57.739 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:5.933
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.005
When I start Tails from USB drive "old" with network unplugged 1:32.745
Then the boot device has safe access rights 2.957
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.530
After features/support/hooks.rb:100 0.046
Tags: @product
2:8.073
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:25.387
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 31.940
And I take note of which tps features are available 1.328
Then a Tails persistence partition exists on USB drive "old" 0.787
And I shutdown Tails and wait for the computer to power off 8.143
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.330
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.720
Then Tails is running from USB drive "old" 1.372
And all tps features are active 2.072
When I write some files expected to persist 1.623
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 2.353
And I take note of which tps features are available 0.437
And I shutdown Tails and wait for the computer to power off 4.289
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.547
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.149
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.522
And I log in to a new session 17.627
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.518
And I plug USB drive "to_upgrade" 2.356
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.038
Then the running Tails is installed on USB drive "to_upgrade" 20.685
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.040
Before features/support/hooks.rb:269 0.004
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.779
Then all tps features from the old Tails version are active 1.564
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.339
And all persistent directories from the old Tails version have safe access rights 2.350
After features/support/hooks.rb:326 0.611
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:16.186
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 11.651
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.494
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.093
And Tor is ready 18.960
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.087
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.153
Given I shutdown Tails and wait for the computer to power off 15.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.172
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.362
When the network is plugged 0.085
And Tor is ready 19.177
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.340
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.381
Given I shutdown Tails and wait for the computer to power off 4.222
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.564
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.005
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.071
And Tor is ready 21.638
Then the Upgrader considers the system as up-to-date 0.318
# 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 14.042
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.913
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
58.026
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 8.926
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 47.844
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.601
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.000