Skip to content

Commit 987d1f3

Browse files
Tests and juniper (#99)
* adding wireless tests * renamed vendor names * testing juniper file * testing with rule_11.py * updated the first rule * adding EXAMPLES.md * updated the URL for EXAMPLES.md * TOC for EXAMPLES.md * Tests and juniper (#96) (#97) * adding wireless tests * renamed vendor names * testing juniper file * testing with rule_11.py * updated the first rule * adding EXAMPLES.md * updated the URL for EXAMPLES.md --------- Co-authored-by: mailsanjayhere <mailsanjayhere@gmail.com> * updating TOC --------- Co-authored-by: mailsanjayhere <mailsanjayhere@gmail.com>
1 parent c8621d3 commit 987d1f3

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

EXAMPLES.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11

2-
<img src="https://netpicker.io/wp-content/uploads/2024/01/netpicker-logo-276x300.png">
2+
<img src="https://netpicker.io/wp-content/uploads/2024/01/netpicker-logo-276x300.png" width="160">
3+
34

45

56

@@ -22,4 +23,10 @@ A set of common Netpicker compliance use-cases.
2223

2324
#### Using Textfsm
2425

26+
## Format of the rules
27+
Understand the Netpicker Rule Structure
28+
29+
Severity Levels: Decide whether your rule should be low, medium, or high severity, depending on its importance.
30+
Rule Naming: Name your rule starting with rule_, followed by a descriptive name that reflects the test's purpose.
31+
Platform Specification: Identify the platforms (e.g., cisco_ios, juniper_junos) the rule applies to.
2532

0 commit comments

Comments
 (0)