Project Number Date
test_Tails_ISO_stable 5289 25 Nov 2024, 12:50

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 22:27.891 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:26.621
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 36.098
When I start Tails from USB drive "old" with network unplugged 1:44.574
Then the boot device has safe access rights 3.497
And Tails is running from USB drive "old" 0.402
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:326 3.753
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.128
Before features/support/hooks.rb:269 0.006
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:31.357
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 32.666
And I take note of which tps features are available 2.077
Then a Tails persistence partition exists on USB drive "old" 1.045
And I shutdown Tails and wait for the computer to power off 7.359
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.015
Tags: @product
2:57.381
Before features/support/hooks.rb:269 0.007
Given a computer 0.263
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.867
Then Tails is running from USB drive "old" 1.077
And all tps features are active 2.369
When I write some files expected to persist 1.852
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.514
And all persistent directories from the old Tails version have safe access rights 2.918
And I take note of which tps features are available 0.505
And I shutdown Tails and wait for the computer to power off 4.783
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.997
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.007
Tags: @product
2:39.096
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.559
And I log in to a new session 21.382
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.810
And I plug USB drive "to_upgrade" 2.527
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.849
Then the running Tails is installed on USB drive "to_upgrade" 25.510
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 3.228
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.988
Before features/support/hooks.rb:269 0.006
Given a computer 0.946
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.196
Then all tps features from the old Tails version are active 1.909
And Tails is running from USB drive "to_upgrade" 0.419
And the boot device has safe access rights 3.740
And the expected persistent files created with the old Tails version are present in the filesystem 1.792
And all persistent directories from the old Tails version have safe access rights 2.981
After features/support/hooks.rb:326 1.220
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
8:51.282
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 34.803
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.547
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.094
And Tor is ready 23.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.172
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.575
Given I shutdown Tails and wait for the computer to power off 1:32.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.282
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 4.275
And the file system changes introduced in version 6.2~testoverlayfs are present 0.393
And only the 6.2~testoverlayfs SquashFS delta is installed 0.116
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.292
When the network is plugged 0.092
And Tor is ready 19.780
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.479
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.423
Given I shutdown Tails and wait for the computer to power off 6.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.412
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 3.545
And the file system changes introduced in version 6.3~testoverlayfs are present 1.308
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.521
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.375
When the network is plugged 0.110
And Tor is ready 21.588
Then the Upgrader considers the system as up-to-date 0.363
# 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 16.104
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.239
After features/support/hooks.rb:326 0.883
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
48.392
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 13.878
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.165
And the signing key used by the Upgrader is outdated 2.308
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 23.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.595
After features/support/hooks.rb:326 0.940
After features/support/hooks.rb:100 0.000