Project Number Date
test_Tails_ISO_stable 5266 15 Nov 2024, 09:00

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 21:41.785 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:25.687
Before features/support/hooks.rb:269 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 35.799
When I start Tails from USB drive "old" with network unplugged 1:43.908
Then the boot device has safe access rights 3.557
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 7.260
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.966
Before features/support/hooks.rb:269 0.004
Given a computer 0.545
And I start Tails from USB drive "old" with network unplugged and I login 1:24.115
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 33.773
And I take note of which tps features are available 1.691
Then a Tails persistence partition exists on USB drive "old" 0.935
And I shutdown Tails and wait for the computer to power off 8.566
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.009
Tags: @product
3:13.046
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.366
Then Tails is running from USB drive "old" 1.362
And all tps features are active 3.021
When I write some files expected to persist 1.858
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.304
And all persistence configuration files have safe access rights 0.538
And all persistent directories from the old Tails version have safe access rights 3.451
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 4.369
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.058
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.231
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 28.324
And I log in to a new session 20.030
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.243
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.142
Then the running Tails is installed on USB drive "to_upgrade" 25.505
And I unplug USB drive "to_upgrade" 0.277
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:326 3.514
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.423
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.175
Then all tps features from the old Tails version are active 1.654
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.902
And the expected persistent files created with the old Tails version are present in the filesystem 2.409
And all persistent directories from the old Tails version have safe access rights 2.704
After features/support/hooks.rb:326 1.168
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:48.793
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 14.845
And no SquashFS delta is installed 0.265
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.510
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.741
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.103
And Tor is ready 25.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.754
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.218
Given I shutdown Tails and wait for the computer to power off 11.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.800
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.754
And the file system changes introduced in version 6.2~testoverlayfs are present 0.461
And only the 6.2~testoverlayfs SquashFS delta is installed 0.126
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.560
# 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.460
When the network is plugged 0.113
And Tor is ready 19.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.765
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.167
Given I shutdown Tails and wait for the computer to power off 59.878
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.220
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.378
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.395
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.098
And Tor is ready 21.025
Then the Upgrader considers the system as up-to-date 0.305
# 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.651
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.121
After features/support/hooks.rb:326 0.703
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
42.637
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 12.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.643
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.805
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 21.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.805
After features/support/hooks.rb:326 0.710
After features/support/hooks.rb:100 0.000