Project Number Date
test_Tails_ISO_stable 4878 08 Jun 2024, 12:33

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:22.837 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:7.562
Before features/support/hooks.rb:269 0.007
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.973
When I start Tails from USB drive "old" with network unplugged 1:31.340
Then the boot device has safe access rights 2.878
And Tails is running from USB drive "old" 0.433
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.076
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:315 3.726
After features/support/hooks.rb:100 0.011
Tags: @product
2:8.223
Before features/support/hooks.rb:269 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:22.625
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 36.634
And I take note of which tps features are available 1.231
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 6.285
After features/support/hooks.rb:315 0.146
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.968
Before features/support/hooks.rb:269 0.005
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.120
Then Tails is running from USB drive "old" 0.370
And all tps features are active 2.152
When I write some files expected to persist 1.791
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.926
And I take note of which tps features are available 0.414
And I shutdown Tails and wait for the computer to power off 4.311
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.053
After features/support/hooks.rb:315 0.098
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.056
Before features/support/hooks.rb:269 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.087
And I log in to a new session 18.668
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.532
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.286
Then the running Tails is installed on USB drive "to_upgrade" 17.276
And I unplug USB drive "to_upgrade" 0.309
And I unplug USB drive "__internal" 0.390
After features/support/hooks.rb:315 3.652
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.724
Before features/support/hooks.rb:269 0.009
Given a computer 0.289
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.528
Then all tps features from the old Tails version are active 1.755
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.142
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.268
After features/support/hooks.rb:315 0.876
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:8.517
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 10.509
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.460
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.042
And Tor is ready 18.763
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.406
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.776
Given I shutdown Tails and wait for the computer to power off 8.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.787
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.903
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.257
When the network is plugged 0.051
And Tor is ready 19.754
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.180
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.032
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.413
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.955
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.033
And Tor is ready 17.619
Then the Upgrader considers the system as up-to-date 0.332
# 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 13.711
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.874
After features/support/hooks.rb:315 0.788
After features/support/hooks.rb:100 0.059
Tags: @product @automatic_upgrade
36.785
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.540
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 1.537
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 18.608
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.670
After features/support/hooks.rb:315 0.703
After features/support/hooks.rb:100 0.000