Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 6 07 Dec 2024, 00:43

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:2.801 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:4.672
Before features/support/hooks.rb:269 0.004
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 31.467
When I start Tails from USB drive "old" with network unplugged 1:27.791
Then the boot device has safe access rights 3.078
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.557
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.739
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 1:35.964
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 31.186
And I take note of which tps features are available 1.477
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 8.672
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.844
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.610
Then Tails is running from USB drive "old" 0.640
And all tps features are active 2.058
When I write some files expected to persist 1.924
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.506
And all persistent directories from the old Tails version have safe access rights 2.549
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.453
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.122
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.857
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 9.864
And I log in to a new session 19.932
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.530
And I plug USB drive "to_upgrade" 2.356
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.931
Then the running Tails is installed on USB drive "to_upgrade" 22.795
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 3.602
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.335
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.251
Then all tps features from the old Tails version are active 1.694
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.466
And the expected persistent files created with the old Tails version are present in the filesystem 1.879
And all persistent directories from the old Tails version have safe access rights 2.495
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:28.739
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 12.381
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.628
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.102
And Tor is ready 21.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.210
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.679
Given I shutdown Tails and wait for the computer to power off 10.906
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.374
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.265
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.264
When the network is plugged 0.074
And Tor is ready 18.481
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.213
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.370
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.780
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.290
And the file system changes introduced in version 6.3~testoverlayfs are present 0.609
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.076
And Tor is ready 18.282
Then the Upgrader considers the system as up-to-date 0.330
# 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.900
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:326 0.849
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.612
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 9.862
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.875
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 18.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.685
After features/support/hooks.rb:326 1.662
After features/support/hooks.rb:100 0.000