Project Number Date
test_Tails_ISO_devel 3556 21 Oct 2024, 13:07

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 18:52.757 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:4.567
Before features/support/hooks.rb:269 0.005
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 30.665
When I start Tails from USB drive "old" with network unplugged 1:28.265
Then the boot device has safe access rights 3.170
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 3.622
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.569
Before features/support/hooks.rb:269 0.007
Given a computer 0.357
And I start Tails from USB drive "old" with network unplugged and I login 1:22.203
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 31.550
And I take note of which tps features are available 1.562
Then a Tails persistence partition exists on USB drive "old" 0.914
And I shutdown Tails and wait for the computer to power off 8.641
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.830
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.074
Then Tails is running from USB drive "old" 0.318
And all tps features are active 1.888
When I write some files expected to persist 1.951
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.601
And I take note of which tps features are available 0.370
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.472
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.427
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 11.731
And I log in to a new session 21.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.316
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.758
Then the running Tails is installed on USB drive "to_upgrade" 18.313
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.256
After features/support/hooks.rb:326 6.959
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.712
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.664
Then all tps features from the old Tails version are active 1.716
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.761
And the expected persistent files created with the old Tails version are present in the filesystem 1.475
And all persistent directories from the old Tails version have safe access rights 2.527
After features/support/hooks.rb:326 0.599
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:24.857
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 12.720
And no SquashFS delta is installed 0.518
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.097
And Tor is ready 17.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.413
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.438
Given I shutdown Tails and wait for the computer to power off 10.918
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.796
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.294
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.328
When the network is plugged 0.064
And Tor is ready 18.287
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.418
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.024
Given I shutdown Tails and wait for the computer to power off 4.115
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.894
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.903
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.071
And Tor is ready 20.067
Then the Upgrader considers the system as up-to-date 0.326
# 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 13.802
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.033
After features/support/hooks.rb:326 0.797
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
36.792
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.911
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.625
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.782
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 18.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.733
After features/support/hooks.rb:326 1.515
After features/support/hooks.rb:100 0.000