Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 3 15 Apr 2025, 21:29

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 21:50.899 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:48.073
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.348
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 1:3.456
When I start Tails from USB drive "old" with network unplugged 1:38.649
Then the boot device has safe access rights 3.342
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.128
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 6.942
After features/support/hooks.rb:100 0.011
Tags: @product
2:16.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.363
And I start Tails from USB drive "old" with network unplugged and I login 1:30.833
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 32.298
And I take note of which tps features are available 2.689
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.772
After features/support/hooks.rb:330 0.263
After features/support/hooks.rb:100 0.011
Tags: @product
3:32.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:46.926
Then Tails is running from USB drive "old" 0.527
And all tps features are active 2.937
When I write some files expected to persist 2.296
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.587
And all persistent directories from the old Tails version have safe access rights 3.281
And I take note of which tps features are available 0.698
And I shutdown Tails and wait for the computer to power off 6.948
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.339
After features/support/hooks.rb:330 0.127
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.275
And I log in to a new session 21.289
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.960
And I plug USB drive "to_upgrade" 2.550
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.325
Then the running Tails is installed on USB drive "to_upgrade" 31.882
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.286
After features/support/hooks.rb:330 2.764
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.083
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.273
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.698
Then all tps features from the old Tails version are active 1.910
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.733
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 2.624
After features/support/hooks.rb:330 1.301
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:10.251
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.398
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.385
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.600
When the network is plugged 0.661
And Tor is ready 22.938
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.925
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.270
Given I shutdown Tails and wait for the computer to power off 9.801
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.715
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.792
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.317
When the network is plugged 0.093
And Tor is ready 22.153
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.662
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.044
Given I shutdown Tails and wait for the computer to power off 6.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.862
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.505
And the file system changes introduced in version 6.3~testoverlayfs are present 0.614
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.345
When the network is plugged 0.071
And Tor is ready 19.052
Then the Upgrader considers the system as up-to-date 0.368
# 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 17.329
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.735
After features/support/hooks.rb:330 0.805
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
38.502
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.168
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.580
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.085
But a current signing key is available on our website 0.000
When the network is plugged 0.151
And Tor is ready 20.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.011
After features/support/hooks.rb:330 0.933
After features/support/hooks.rb:100 0.000