Project Number Date
test_Tails_ISO_20666-whisperback-search 1 16 Nov 2024, 20:25

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:55.979 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:48.419
Before features/support/hooks.rb:269 0.006
Given a computer 1.374
And I create a 7200 MiB disk named "old" 0.487
And I plug USB drive "old" 1.111
And I write an old version of the Tails USB image to disk "old" 52.391
When I start Tails from USB drive "old" with network unplugged 1:48.189
Then the boot device has safe access rights 3.671
And Tails is running from USB drive "old" 0.429
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:326 7.460
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.201
Before features/support/hooks.rb:269 0.006
Given a computer 0.381
And I start Tails from USB drive "old" with network unplugged and I login 1:33.005
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 36.419
And I take note of which tps features are available 2.272
Then a Tails persistence partition exists on USB drive "old" 0.950
And I shutdown Tails and wait for the computer to power off 8.772
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.009
Tags: @product
3:21.810
Before features/support/hooks.rb:269 0.005
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:39.760
Then Tails is running from USB drive "old" 0.460
And all tps features are active 2.893
When I write some files expected to persist 2.290
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.303
And all persistence configuration files have safe access rights 0.515
And all persistent directories from the old Tails version have safe access rights 3.204
And I take note of which tps features are available 0.712
And I shutdown Tails and wait for the computer to power off 4.777
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.625
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.009
Tags: @product
3:13.679
Before features/support/hooks.rb:269 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 27.103
And I log in to a new session 22.150
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.041
And I plug USB drive "to_upgrade" 2.597
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.115
Then the running Tails is installed on USB drive "to_upgrade" 21.897
And I unplug USB drive "to_upgrade" 0.468
And I unplug USB drive "__internal" 0.305
After features/support/hooks.rb:326 3.744
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.421
Before features/support/hooks.rb:269 0.008
Given a computer 0.359
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.466
Then all tps features from the old Tails version are active 3.244
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.123
And the expected persistent files created with the old Tails version are present in the filesystem 1.427
And all persistent directories from the old Tails version have safe access rights 2.443
After features/support/hooks.rb:326 1.125
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:46.053
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 31.575
And no SquashFS delta is installed 0.229
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.085
And Tor is ready 26.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.158
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.071
Given I shutdown Tails and wait for the computer to power off 11.588
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.689
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.622
And the file system changes introduced in version 6.2~testoverlayfs are present 0.386
And only the 6.2~testoverlayfs SquashFS delta is installed 0.103
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.307
When the network is plugged 0.102
And Tor is ready 47.918
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.618
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.241
Given I shutdown Tails and wait for the computer to power off 4.673
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.034
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 2.276
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.412
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.326
When the network is plugged 0.090
And Tor is ready 18.248
Then the Upgrader considers the system as up-to-date 0.367
# 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 15.172
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.207
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
44.393
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 10.872
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.790
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 28.241
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.891
After features/support/hooks.rb:326 0.777
After features/support/hooks.rb:100 0.000