mirror of
https://github.com/kernelkit/infix.git
synced 2026-08-04 06:43:00 +02:00
added missing test-spec files
Signed-off-by: Ejub Sabic <ejub1946@outlook.com>
This commit is contained in:
@@ -1,34 +0,0 @@
|
||||
=== Boot From Factory Config
|
||||
|
||||
ifdef::topdoc[:imagesdir: {topdoc}../../test/case/system/factory_config]
|
||||
|
||||
==== Description
|
||||
|
||||
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.
|
||||
|
||||
This exercises the device's own first-boot bootstrap path: with no
|
||||
startup-config present, confd initialises running from the factory-config.
|
||||
That is exactly what a factory-fresh (or factory-reset) device does, and
|
||||
it avoids applying a full config swap over the live management session.
|
||||
|
||||
The test is image-generic: it uses 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 topology is used on purpose: a factory config is not written
|
||||
with a lab full of peers in mind, so applying it across a multi-node
|
||||
topology could trigger broadcast storms or similar.
|
||||
|
||||
==== Topology
|
||||
|
||||
image::topology.svg[Boot From Factory Config topology, align=center, scaledwidth=75%]
|
||||
|
||||
==== Sequence
|
||||
|
||||
. Set up topology and attach to target DUT
|
||||
. Determine factory-config hostname
|
||||
. Clear startup-config so the device boots from factory
|
||||
. Reboot onto the factory config
|
||||
. Verify device is usable and not in failure-config
|
||||
@@ -0,0 +1 @@
|
||||
test.adoc
|
||||
@@ -0,0 +1,24 @@
|
||||
=== Boot From Factory Config
|
||||
|
||||
ifdef::topdoc[:imagesdir: {topdoc}../../test/case/system/factory_config]
|
||||
|
||||
==== Description
|
||||
|
||||
Verify that the device boots cleanly from its factory-config and stays
|
||||
usable, i.e. it does not fall back to the fail-secure failure-config.
|
||||
Clearing the startup-config makes confd bootstrap running from the
|
||||
factory-config on the next boot, as on a factory-fresh device.
|
||||
|
||||
==== Topology
|
||||
|
||||
image::topology.svg[Boot From Factory Config topology, align=center, scaledwidth=75%]
|
||||
|
||||
==== Sequence
|
||||
|
||||
. Set up topology and attach to target DUT
|
||||
. Determine factory-config hostname
|
||||
. Clear startup-config so the device boots from factory
|
||||
. Reboot onto the factory config
|
||||
. Verify device is usable and not in failure-config
|
||||
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
|
||||
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
|
||||
"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
|
||||
<!-- Generated by graphviz version 2.43.0 (0)
|
||||
-->
|
||||
|
||||
<!-- Title: 1x1 Pages: 1 -->
|
||||
<svg width="424pt" height="45pt"
|
||||
viewBox="0.00 0.00 424.03 45.00" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
|
||||
|
||||
|
Before Width: | Height: | Size: 1.7 KiB After Width: | Height: | Size: 1.6 KiB |
Reference in New Issue
Block a user