Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 14 12 Dec 2024, 00:22

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 19:4.476 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.163
Before features/support/hooks.rb:269 0.004
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.941
When I start Tails from USB drive "old" with network unplugged 1:34.142
Then the boot device has safe access rights 2.848
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.509
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.293
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:26.639
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 31.980
And I take note of which tps features are available 2.019
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 8.340
After features/support/hooks.rb:326 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.546
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.160
Then Tails is running from USB drive "old" 0.382
And all tps features are active 1.820
When I write some files expected to persist 1.967
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.536
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.343
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.095
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.350
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.281
And I log in to a new session 20.635
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.691
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.749
Then the running Tails is installed on USB drive "to_upgrade" 21.048
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.278
After features/support/hooks.rb:326 6.952
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.728
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.382
Then all tps features from the old Tails version are active 1.634
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.427
And the expected persistent files created with the old Tails version are present in the filesystem 1.442
And all persistent directories from the old Tails version have safe access rights 2.317
After features/support/hooks.rb:326 0.645
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:31.087
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.911
And no SquashFS delta is installed 0.531
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.089
And Tor is ready 24.240
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.572
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.206
Given I shutdown Tails and wait for the computer to power off 10.618
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.278
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.450
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.282
When the network is plugged 0.065
And Tor is ready 18.284
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.829
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.486
Given I shutdown Tails and wait for the computer to power off 4.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.206
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.071
And Tor is ready 19.484
Then the Upgrader considers the system as up-to-date 0.325
# 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.809
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.958
After features/support/hooks.rb:326 0.774
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.308
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.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.663
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.764
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 19.436
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.212
After features/support/hooks.rb:326 0.941
After features/support/hooks.rb:100 0.000