Project Number Date
test_Tails_ISO_devel 3575 03 Nov 2024, 12:54

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 20:15.330 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:21.560
Before features/support/hooks.rb:269 0.008
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 35.139
When I start Tails from USB drive "old" with network unplugged 1:40.691
Then the boot device has safe access rights 3.332
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:326 3.551
After features/support/hooks.rb:100 0.045
Tags: @product
2:26.643
Before features/support/hooks.rb:269 0.008
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:40.450
Then Tails is running from USB drive "old" 0.438
And I create a persistent partition 32.971
And I take note of which tps features are available 2.570
Then a Tails persistence partition exists on USB drive "old" 0.986
And I shutdown Tails and wait for the computer to power off 9.005
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.744
Before features/support/hooks.rb:269 0.004
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.230
Then Tails is running from USB drive "old" 0.388
And all tps features are active 2.491
When I write some files expected to persist 1.972
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.704
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 4.508
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.083
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.013
Tags: @product
2:37.774
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 12.688
And I log in to a new session 18.789
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.716
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.413
Then the running Tails is installed on USB drive "to_upgrade" 22.306
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:326 2.606
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.180
Before features/support/hooks.rb:269 0.010
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.060
Then all tps features from the old Tails version are active 1.877
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.591
And all persistent directories from the old Tails version have safe access rights 2.561
After features/support/hooks.rb:326 0.889
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:42.348
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.521
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.336
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.076
And Tor is ready 22.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.647
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.112
Given I shutdown Tails and wait for the computer to power off 10.810
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.032
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.546
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
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.391
# 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.350
When the network is plugged 0.074
And Tor is ready 19.782
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.778
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.846
Given I shutdown Tails and wait for the computer to power off 4.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.991
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.315
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.373
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.342
When the network is plugged 0.104
And Tor is ready 20.193
Then the Upgrader considers the system as up-to-date 0.333
# 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.557
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.246
After features/support/hooks.rb:326 0.878
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.079
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 11.713
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.671
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.854
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 20.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.523
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000