Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 18 13 Dec 2024, 16:46

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:53.097 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:12.955
Before features/support/hooks.rb:269 0.006
Given a computer 0.563
And I create a 7200 MiB disk named "old" 0.334
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 35.753
When I start Tails from USB drive "old" with network unplugged 1:30.835
Then the boot device has safe access rights 3.314
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 7.130
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.382
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:35.552
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 34.574
And I take note of which tps features are available 2.132
Then a Tails persistence partition exists on USB drive "old" 0.918
And I shutdown Tails and wait for the computer to power off 8.632
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.898
Before features/support/hooks.rb:269 0.005
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.390
Then Tails is running from USB drive "old" 0.868
And all tps features are active 2.066
When I write some files expected to persist 3.219
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 3.691
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.365
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.926
After features/support/hooks.rb:326 0.099
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.876
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 11.563
And I log in to a new session 18.977
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.730
And I plug USB drive "to_upgrade" 2.495
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.533
Then the running Tails is installed on USB drive "to_upgrade" 25.055
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.294
After features/support/hooks.rb:326 3.554
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.398
Before features/support/hooks.rb:269 0.004
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.566
Then all tps features from the old Tails version are active 1.638
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 3.568
And the expected persistent files created with the old Tails version are present in the filesystem 1.614
And all persistent directories from the old Tails version have safe access rights 2.410
After features/support/hooks.rb:326 0.902
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:46.714
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.135
And no SquashFS delta is installed 0.468
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.071
And Tor is ready 21.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.770
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.395
Given I shutdown Tails and wait for the computer to power off 9.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.886
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.261
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# 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.278
When the network is plugged 0.080
And Tor is ready 20.483
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.761
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.822
Given I shutdown Tails and wait for the computer to power off 4.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.984
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.301
And the file system changes introduced in version 6.3~testoverlayfs are present 0.636
And only the 6.3~testoverlayfs SquashFS delta is installed 0.113
# 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.401
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.374
When the network is plugged 0.153
And Tor is ready 21.946
Then the Upgrader considers the system as up-to-date 0.371
# 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 15.165
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.953
After features/support/hooks.rb:326 0.855
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.871
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.390
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.907
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 19.635
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.439
After features/support/hooks.rb:326 1.937
After features/support/hooks.rb:100 0.000