Project Number Date
test_Tails_ISO_devel 3469 08 Aug 2024, 12:43

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:14.644 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:49.404
Before features/support/hooks.rb:269 0.008
Given a computer 0.276
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 55.339
When I start Tails from USB drive "old" with network unplugged 1:48.338
Then the boot device has safe access rights 3.234
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.133
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.813
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.104
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 1:33.173
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 40.328
And I take note of which tps features are available 2.404
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 8.693
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.978
Before features/support/hooks.rb:269 0.010
Given a computer 0.275
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.520
Then Tails is running from USB drive "old" 0.343
And all tps features are active 2.306
When I write some files expected to persist 1.635
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.844
And I take note of which tps features are available 0.632
And I shutdown Tails and wait for the computer to power off 4.630
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.166
After features/support/hooks.rb:326 0.201
After features/support/hooks.rb:100 0.015
Tags: @product
2:54.057
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 21.736
And I log in to a new session 21.797
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.293
And I plug USB drive "to_upgrade" 2.481
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.183
Then the running Tails is installed on USB drive "to_upgrade" 23.075
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:326 2.858
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.525
Before features/support/hooks.rb:269 0.006
Given a computer 0.527
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.337
Then all tps features from the old Tails version are active 1.704
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 2.954
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 2.323
After features/support/hooks.rb:326 0.591
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:4.648
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 25.535
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.397
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.082
And Tor is ready 20.094
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.831
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.249
Given I shutdown Tails and wait for the computer to power off 12.208
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.952
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.375
And the file system changes introduced in version 6.2~testoverlayfs are present 0.394
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.399
# 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.274
When the network is plugged 0.071
And Tor is ready 16.483
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.855
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.921
Given I shutdown Tails and wait for the computer to power off 4.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.851
Then Tails is running version 6.3~testoverlayfs 0.038
And all tps features are active 2.348
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.485
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.470
When the network is plugged 0.088
And Tor is ready 18.588
Then the Upgrader considers the system as up-to-date 0.408
# 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.915
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.158
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
36.925
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 10.870
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 1.159
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 16.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.453
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.000