clixon/test
2019-01-05 11:08:16 +01:00
..
all.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
Jenkinsfile
lib.sh netconf error handling and test summary script 2018-12-21 14:44:59 +01:00
nacm.sh
plot_perf.sh
README.md netconf error handling and test summary script 2018-12-21 14:44:59 +01:00
test_choice.sh Validation of mandatory choice and recursive mandatory containers. 2019-01-05 11:08:16 +01:00
test_cli.sh CLICON_XML_SORT option (in clixon-config.yang) has been removed and set to true permanently since setting it to false is obsolete. 2019-01-02 17:43:58 +01:00
test_compat.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_datastore.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_feature.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_identity.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_install.sh Added new clixon-lib yang module for internal netconf protocol. Currently only extends the standard with a debug RPC. 2019-01-02 22:50:03 +01:00
test_json.sh
test_leafref.sh Yang choice functionality improved and stricter validation for CLI generation, mandatory flags, etc. 2019-01-04 11:37:26 +01:00
test_list.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_nacm.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_nacm_ext.sh Validation of mandatory choice and recursive mandatory containers. 2019-01-05 11:08:16 +01:00
test_nacm_protocol.sh Validation of mandatory choice and recursive mandatory containers. 2019-01-05 11:08:16 +01:00
test_netconf.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_openconfig.sh Validation of mandatory choice and recursive mandatory containers. 2019-01-05 11:08:16 +01:00
test_order.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_perf.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_restconf.sh Validation of mandatory choice and recursive mandatory containers. 2019-01-05 11:08:16 +01:00
test_restconf2.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_rpc.sh Validation of mandatory choice and recursive mandatory containers. 2019-01-05 11:08:16 +01:00
test_startup.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_stream.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_type.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_union.sh * More precise Yang validation and better error messages 2018-12-21 01:33:41 +01:00
test_when_must.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_xml.sh
test_xpath.sh
test_yang.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_yang_load.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_yang_namespace.sh * Strict namespace setting can be a problem when upgrading existing database files, such as startup-db or persistent running-db, or any other saved XML file. 2019-01-02 15:18:29 +01:00
test_yang_parse.sh

Clixon tests

This directory contains testing code for clixon and the example application. Assumes setup of http daemon as describe under apps/restonf

  • clixon A top-level script clones clixon in /tmp and starts all.sh. You can copy this file (review it first) and place as cron script
  • all.sh Run through all tests named 'test*.sh' in this directory. Therefore, if you place a test in this directory matching 'test*.sh' it will be run automatically. By default the script will exit on first error. Run as all.sh summary to continue and print a summary on all tests.
  • test_nacm.sh Auth tests using internal NACM
  • test_nacm_ext.sh Auth tests using external NACM (separate file)
  • test_cli.sh CLI tests
  • test_netconf.sh Netconf tests
  • test_restconf.sh Restconf tests
  • test_yang.sh Yang tests for constructs not in the example.
  • test_leafref.sh Yang leafref tests
  • test_datastore.sh Datastore tests

Example runs:

> run.sh
# Runs through all tests matching 'test_*.sh' in the directory. Prints test output
# and stops on first error

> run.sh summary
# Same as above but continues after errors and does not print test output.