Project Number Date
test_Tails_ISO_stable 5022 12 Aug 2024, 14:58

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:42.993 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:15.609
Before features/support/hooks.rb:269 0.008
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.453
When I start Tails from USB drive "old" with network unplugged 1:38.564
Then the boot device has safe access rights 3.991
And Tails is running from USB drive "old" 0.419
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.408
And I unplug USB drive "old" 0.263
After features/support/hooks.rb:326 7.271
After features/support/hooks.rb:100 0.017
Tags: @product
2:21.610
Before features/support/hooks.rb:269 0.012
Given a computer 0.305
And I start Tails from USB drive "old" with network unplugged and I login 1:35.754
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 32.181
And I take note of which tps features are available 2.710
Then a Tails persistence partition exists on USB drive "old" 1.014
And I shutdown Tails and wait for the computer to power off 9.244
After features/support/hooks.rb:326 0.272
After features/support/hooks.rb:100 0.015
Tags: @product
3:14.317
Before features/support/hooks.rb:269 0.012
Given a computer 0.327
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.168
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.467
When I write some files expected to persist 2.179
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.382
And all persistence configuration files have safe access rights 0.528
And all persistent directories from the old Tails version have safe access rights 2.661
And I take note of which tps features are available 0.606
And I shutdown Tails and wait for the computer to power off 4.365
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.273
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.012
Tags: @product
2:39.329
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.713
And I log in to a new session 20.159
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.341
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.812
Then the running Tails is installed on USB drive "to_upgrade" 20.451
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 3.743
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.172
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.356
Then all tps features from the old Tails version are active 1.500
And Tails is running from USB drive "to_upgrade" 0.412
And the boot device has safe access rights 3.275
And the expected persistent files created with the old Tails version are present in the filesystem 1.820
And all persistent directories from the old Tails version have safe access rights 2.560
After features/support/hooks.rb:326 0.621
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:19.748
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.148
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.402
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.602
When the network is plugged 0.206
And Tor is ready 49.045
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.608
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.683
Given I shutdown Tails and wait for the computer to power off 10.915
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.634
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.384
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.312
When the network is plugged 0.087
And Tor is ready 44.659
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.654
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.634
Given I shutdown Tails and wait for the computer to power off 4.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.955
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.072
And Tor is ready 19.754
Then the Upgrader considers the system as up-to-date 0.316
# 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.697
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.009
After features/support/hooks.rb:326 0.824
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
32.204
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.706
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.872
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 14.721
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.445
After features/support/hooks.rb:326 1.133
After features/support/hooks.rb:100 0.000