Files
Richard Alpe d333c66f9c test: add generic boot-from-factory-config test
Verify that the device's factory-default configuration boots cleanly and
that the device remains usable afterwards -- i.e. it does not fall back to
the fail-secure failure-config.

The test exercises the device's own first-boot bootstrap path: it clears
the startup-config and reboots with the test-mode startup override set, so
confd initialises running from the factory-config (its first-boot path).
That mirrors a factory-fresh / factory-reset device and avoids applying a
full config swap over the live management session -- confd cannot replace
the whole running datastore from within an RPC without timing out, and a
factory config may reconfigure the very transport we are connected over.

The test is image-generic, using whatever factory-config the running image
was built with, so it covers both the stock Infix factory config and any
spin factory config. A single-node (1x1) topology is used on purpose: a
factory config is not written with a lab full of peers in mind, so booting
it across a multi-node topology could trigger broadcast storms or similar.
NETCONF only, as it is the one management transport present in every
factory config.

Signed-off-by: Richard Alpe <richard@bit42.se>
2026-06-30 10:32:43 +02:00

31 lines
586 B
YAML

---
- name: Set Hostname
case: hostname/test.py
- name: Add/Delete User
case: add_delete_user/test.py
- name: Add Admin User
case: user_admin/test.py
- name: Basic NACM Permissions
case: nacm-basic/test.py
- name: Set Timezone Using Timezone Name
case: timezone/test.py
- name: Set Timezone with UTC Offset
case: timezone_utc_offset/test.py
- name: Basic NTP Client Test
case: ntp_client/test.py
- name: System Upgrade
case: upgrade/test.py
- name: Schedule Reboot
case: schedule_reboot/test.py
- name: Boot From Factory Config
case: factory_config/test.py