Project Number Date
test_Tails_ISO_devel 3458 12 Jul 2024, 00:37

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 20:28.177 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:33.258
Before features/support/hooks.rb:269 0.005
Given a computer 0.286
And I create a 7200 MiB disk named "old" 0.171
And I plug USB drive "old" 1.105
And I write an old version of the Tails USB image to disk "old" 31.103
When I start Tails from USB drive "old" with network unplugged 1:56.369
Then the boot device has safe access rights 3.131
And Tails is running from USB drive "old" 0.399
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.556
After features/support/hooks.rb:100 0.013
Tags: @product
2:16.755
Before features/support/hooks.rb:269 0.008
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:31.442
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 33.386
And I take note of which tps features are available 1.865
Then a Tails persistence partition exists on USB drive "old" 0.854
And I shutdown Tails and wait for the computer to power off 8.624
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.010
Tags: @product
3:7.277
Before features/support/hooks.rb:269 0.008
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.773
Then Tails is running from USB drive "old" 0.353
And all tps features are active 2.476
When I write some files expected to persist 1.960
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.274
And all persistence configuration files have safe access rights 0.518
And all persistent directories from the old Tails version have safe access rights 2.719
And I take note of which tps features are available 0.640
And I shutdown Tails and wait for the computer to power off 4.306
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.007
After features/support/hooks.rb:326 0.116
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.592
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 36.306
And I log in to a new session 19.466
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.446
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.035
Then the running Tails is installed on USB drive "to_upgrade" 20.250
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.439
After features/support/hooks.rb:326 4.147
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.591
Before features/support/hooks.rb:269 0.009
Given a computer 0.643
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.101
Then all tps features from the old Tails version are active 2.231
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.916
And the expected persistent files created with the old Tails version are present in the filesystem 1.700
And all persistent directories from the old Tails version have safe access rights 2.646
After features/support/hooks.rb:326 0.879
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
6:39.525
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.845
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.981
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.531
When the network is plugged 0.057
And Tor is ready 22.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.485
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.877
Given I shutdown Tails and wait for the computer to power off 10.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.484
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.370
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.267
When the network is plugged 0.048
And Tor is ready 20.300
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.219
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.221
Given I shutdown Tails and wait for the computer to power off 4.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.265
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.244
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.364
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.381
When the network is plugged 0.044
And Tor is ready 21.867
Then the Upgrader considers the system as up-to-date 0.356
# 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.421
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.080
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.175
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 11.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.835
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 18.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.003
After features/support/hooks.rb:326 0.675
After features/support/hooks.rb:100 0.000