Skip to content

Commit

Permalink
Tests and juniper (#99)
Browse files Browse the repository at this point in the history
* 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>
  • Loading branch information
2 people authored and imi committed Oct 10, 2024
1 parent 2b0be67 commit 3e3dc9d
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion EXAMPLES.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@

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




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

#### Using Textfsm

## Format of the rules
Understand the Netpicker Rule Structure

Severity Levels: Decide whether your rule should be low, medium, or high severity, depending on its importance.
Rule Naming: Name your rule starting with rule_, followed by a descriptive name that reflects the test's purpose.
Platform Specification: Identify the platforms (e.g., cisco_ios, juniper_junos) the rule applies to.

0 comments on commit 3e3dc9d

Please sign in to comment.