Project Number Date
test_Tails_ISO_devel 3459 12 Jul 2024, 03:03

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:9.651 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:42.844
Before features/support/hooks.rb:269 0.006
Given a computer 0.244
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 33.478
When I start Tails from USB drive "old" with network unplugged 2:3.270
Then the boot device has safe access rights 3.607
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.394
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 3.601
After features/support/hooks.rb:100 0.013
Tags: @product
2:7.806
Before features/support/hooks.rb:269 0.010
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login 1:22.420
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 33.151
And I take note of which tps features are available 1.996
Then a Tails persistence partition exists on USB drive "old" 0.964
And I shutdown Tails and wait for the computer to power off 8.691
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.011
Tags: @product
2:44.320
Before features/support/hooks.rb:269 0.008
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.238
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.152
When I write some files expected to persist 1.900
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.329
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.732
And I take note of which tps features are available 0.541
And I shutdown Tails and wait for the computer to power off 5.417
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.996
After features/support/hooks.rb:326 0.138
After features/support/hooks.rb:100 0.013
Tags: @product
2:31.410
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.285
And I log in to a new session 19.687
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.538
And I plug USB drive "to_upgrade" 2.431
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.619
Then the running Tails is installed on USB drive "to_upgrade" 17.424
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 7.583
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.284
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.592
Then all tps features from the old Tails version are active 1.704
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.546
And all persistent directories from the old Tails version have safe access rights 2.488
After features/support/hooks.rb:326 0.692
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:13.690
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.451
And no SquashFS delta is installed 0.359
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.046
And Tor is ready 20.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.873
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.706
Given I shutdown Tails and wait for the computer to power off 8.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.774
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.527
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.417
# 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.284
When the network is plugged 0.042
And Tor is ready 17.329
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.341
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.586
Given I shutdown Tails and wait for the computer to power off 5.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.011
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.231
And the file system changes introduced in version 6.3~testoverlayfs are present 0.612
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.044
And Tor is ready 19.190
Then the Upgrader considers the system as up-to-date 0.339
# 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.345
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.082
After features/support/hooks.rb:326 0.796
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.294
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 0.813
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 20.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.687
After features/support/hooks.rb:326 0.676
After features/support/hooks.rb:100 0.000