Project Number Date
test_Tails_ISO_20666-whisperback-search 15 21 Nov 2024, 22:41

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:49.781 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:14.572
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.543
When I start Tails from USB drive "old" with network unplugged 1:35.779
Then the boot device has safe access rights 2.943
And Tails is running from USB drive "old" 0.375
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.277
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.540
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.016
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:32.796
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 32.884
And I take note of which tps features are available 1.831
Then a Tails persistence partition exists on USB drive "old" 0.739
And I shutdown Tails and wait for the computer to power off 8.205
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.269
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.896
Then Tails is running from USB drive "old" 1.098
And all tps features are active 2.005
When I write some files expected to persist 1.680
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.727
And all persistence configuration files have safe access rights 0.796
And all persistent directories from the old Tails version have safe access rights 3.518
And I take note of which tps features are available 0.416
And I shutdown Tails and wait for the computer to power off 4.401
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.540
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.890
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 10.624
And I log in to a new session 20.251
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.860
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.428
Then the running Tails is installed on USB drive "to_upgrade" 24.913
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 3.340
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.518
Before features/support/hooks.rb:269 0.006
Given a computer 0.239
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.091
Then all tps features from the old Tails version are active 1.768
And Tails is running from USB drive "to_upgrade" 0.498
And the boot device has safe access rights 3.083
And the expected persistent files created with the old Tails version are present in the filesystem 1.409
And all persistent directories from the old Tails version have safe access rights 2.427
After features/support/hooks.rb:326 0.588
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:38.649
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 26.056
And no SquashFS delta is installed 0.308
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.244
When the network is plugged 0.084
And Tor is ready 21.279
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.090
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.562
Given I shutdown Tails and wait for the computer to power off 8.652
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.840
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
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.334
# 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.286
When the network is plugged 0.067
And Tor is ready 17.502
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.640
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.937
Given I shutdown Tails and wait for the computer to power off 4.278
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.888
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.959
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.077
And Tor is ready 21.702
Then the Upgrader considers the system as up-to-date 0.314
# 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.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.996
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
57.864
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 9.735
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.686
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.784
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 45.916
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000