Project Number Date
test_Tails_ISO_devel 3359 21 Apr 2024, 12:24

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:46.342 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:0.152
Before features/support/hooks.rb:259 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.015
When I start Tails from USB drive "old" with network unplugged 1:25.669
Then the boot device has safe access rights 3.140
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:305 6.961
After features/support/hooks.rb:89 0.012
Tags: @product
1:59.197
Before features/support/hooks.rb:259 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:16.662
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 33.425
And I take note of which tps features are available 1.344
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 6.379
After features/support/hooks.rb:305 0.183
After features/support/hooks.rb:89 0.011
Tags: @product
2:45.580
Before features/support/hooks.rb:259 0.007
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.203
Then Tails is running from USB drive "old" 0.406
And all tps features are active 2.153
When I write some files expected to persist 1.787
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.494
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.366
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.906
After features/support/hooks.rb:305 0.139
After features/support/hooks.rb:89 0.011
Tags: @product
2:35.644
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.537
And I log in to a new session 25.789
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.312
And I plug USB drive "to_upgrade" 2.602
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.698
Then the running Tails is installed on USB drive "to_upgrade" 22.320
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.172
After features/support/hooks.rb:305 2.478
After features/support/hooks.rb:89 0.000
Tags: @product
2:10.877
Before features/support/hooks.rb:259 0.007
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.788
Then all tps features from the old Tails version are active 1.552
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.155
And the expected persistent files created with the old Tails version are present in the filesystem 1.624
And all persistent directories from the old Tails version have safe access rights 2.223
After features/support/hooks.rb:305 0.637
After features/support/hooks.rb:89 0.012
Tags: @product @automatic_upgrade
6:17.390
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.948
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.042
And Tor is ready 19.544
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.370
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.243
Given I shutdown Tails and wait for the computer to power off 8.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.686
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.088
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.413
# 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.262
When the network is plugged 0.051
And Tor is ready 21.068
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.195
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.492
Given I shutdown Tails and wait for the computer to power off 4.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.727
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.431
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.069
And Tor is ready 20.453
Then the Upgrader considers the system as up-to-date 0.294
# 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.921
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.052
After features/support/hooks.rb:305 0.803
After features/support/hooks.rb:89 0.021
Tags: @product @automatic_upgrade
57.498
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.909
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 45.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.561
After features/support/hooks.rb:305 0.706
After features/support/hooks.rb:89 0.000