Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 34 20 Dec 2024, 00:19

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:26.065 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.850
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.097
When I start Tails from USB drive "old" with network unplugged 1:39.180
Then the boot device has safe access rights 3.172
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.244
After features/support/hooks.rb:326 7.172
After features/support/hooks.rb:100 0.035
Tags: @product
2:20.496
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:36.714
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 32.217
And I take note of which tps features are available 1.943
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 8.217
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.579
Before features/support/hooks.rb:269 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.359
Then Tails is running from USB drive "old" 1.529
And all tps features are active 2.156
When I write some files expected to persist 1.926
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 5.018
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 4.321
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.918
After features/support/hooks.rb:326 0.237
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.487
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.843
And I log in to a new session 18.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.408
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.790
Then the running Tails is installed on USB drive "to_upgrade" 25.110
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 4.627
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.567
Before features/support/hooks.rb:269 0.005
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.316
Then all tps features from the old Tails version are active 1.710
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.280
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.332
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:33.923
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 26.867
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.073
And Tor is ready 20.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.604
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.080
Given I shutdown Tails and wait for the computer to power off 8.696
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.646
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.279
When the network is plugged 0.084
And Tor is ready 17.452
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.770
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.717
Given I shutdown Tails and wait for the computer to power off 4.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.072
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.097
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.256
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.423
When the network is plugged 0.070
And Tor is ready 19.554
Then the Upgrader considers the system as up-to-date 0.309
# 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.180
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.082
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
34.161
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 10.225
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 16.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.534
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.000