Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 2 06 Dec 2024, 01:10

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:34.276 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:16.604
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.719
When I start Tails from USB drive "old" with network unplugged 1:39.292
Then the boot device has safe access rights 3.248
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:330 3.748
After features/support/hooks.rb:100 0.010
Tags: @product
2:3.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:22.305
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 30.535
And I take note of which tps features are available 1.571
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.245
After features/support/hooks.rb:330 0.192
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.682
Then Tails is running from USB drive "old" 0.493
And all tps features are active 2.102
When I write some files expected to persist 1.756
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.342
And all persistent directories from the old Tails version have safe access rights 2.646
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.296
After features/support/hooks.rb:330 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 11.917
And I log in to a new session 23.624
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.806
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.930
Then the running Tails is installed on USB drive "to_upgrade" 18.277
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 5.244
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.965
Then all tps features from the old Tails version are active 1.689
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 3.300
And the expected persistent files created with the old Tails version are present in the filesystem 2.568
And all persistent directories from the old Tails version have safe access rights 2.711
After features/support/hooks.rb:330 0.717
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:45.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.333
And no SquashFS delta is installed 0.689
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
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.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.083
And Tor is ready 20.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.975
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.055
Given I shutdown Tails and wait for the computer to power off 10.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.812
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.293
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.520
# 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.381
When the network is plugged 0.121
And Tor is ready 18.599
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.820
Given I shutdown Tails and wait for the computer to power off 4.417
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.436
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.609
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.072
And Tor is ready 18.786
Then the Upgrader considers the system as up-to-date 10.780
# 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.459
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.268
After features/support/hooks.rb:330 0.919
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.227
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.710
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the signing key used by the Upgrader is outdated 1.381
But a current signing key is available on our website 0.000
When the network is plugged 0.100
And Tor is ready 17.734
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.797
After features/support/hooks.rb:330 0.643
After features/support/hooks.rb:100 0.000