Project Number Date
test_Tails_ISO_stable 4936 12 Jul 2024, 02:50

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:40.320 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:10.618
Before features/support/hooks.rb:269 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 33.663
When I start Tails from USB drive "old" with network unplugged 1:31.743
Then the boot device has safe access rights 2.943
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 7.964
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.110
Before features/support/hooks.rb:269 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:21.883
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 31.172
And I take note of which tps features are available 2.154
Then a Tails persistence partition exists on USB drive "old" 0.911
And I shutdown Tails and wait for the computer to power off 8.476
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.599
Before features/support/hooks.rb:269 0.006
Given a computer 0.782
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.525
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.104
When I write some files expected to persist 2.228
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.770
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.325
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.010
Tags: @product
2:21.379
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.110
And I log in to a new session 16.680
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.341
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.468
Then the running Tails is installed on USB drive "to_upgrade" 16.891
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:326 2.039
After features/support/hooks.rb:100 0.000
Tags: @product
2:1.931
Before features/support/hooks.rb:269 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 1:52.636
Then all tps features from the old Tails version are active 1.665
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 2.959
And the expected persistent files created with the old Tails version are present in the filesystem 1.524
And all persistent directories from the old Tails version have safe access rights 2.663
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
6:38.960
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 10.840
And no SquashFS delta is installed 0.282
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.203
And Tor is ready 19.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.228
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.572
Given I shutdown Tails and wait for the computer to power off 10.763
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.911
Then Tails is running version 6.2~testoverlayfs 0.121
And all tps features are active 3.790
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.368
# 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.465
And Tor is ready 18.868
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.149
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.683
Given I shutdown Tails and wait for the computer to power off 4.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.538
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.805
And the file system changes introduced in version 6.3~testoverlayfs are present 0.669
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.048
And Tor is ready 20.927
Then the Upgrader considers the system as up-to-date 0.319
# 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.338
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.943
After features/support/hooks.rb:326 0.908
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.719
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 12.408
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.558
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.753
But a current signing key is available on our website 0.000
When the network is plugged 0.407
And Tor is ready 18.019
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.509
After features/support/hooks.rb:326 0.912
After features/support/hooks.rb:100 0.000