You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/development/testing_framework.rst
+44-11
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
Testing Framework
2
2
-----------------
3
3
4
-
As napalm consists of multiple drivers and all of them have to provide similar functionality, we have developed a testing framework to provide a consistent test suite for all the drivers.
4
+
As NAPALM consists of multiple drivers and all of them have to provide similar functionality, we have developed a testing framework to provide a consistent test suite for all the drivers.
5
5
6
6
Features
7
7
________
@@ -42,7 +42,7 @@ By default, the tests are going to be run against mocked data but you can change
42
42
* ``NAPALM_USERNAME``
43
43
* ``NAPALM_PASSWORD``
44
44
* ``NAPALM_OPTIONAL_ARGS``
45
-
45
+
46
46
Mocking the ``open`` method
47
47
^^^^^^^^^^^^^^^^^^^^^^^^^^^
48
48
@@ -56,29 +56,29 @@ Multiple test cases::
56
56
(napalm) ➜ napalm-eos git:(test_framework) ✗ ls test/unit/mocked_data/test_get_bgp_neighbors
* :code:`eos_fn0039_config` (eos) - Transform old style configuration to the new style, available beginning with EOS release 4.23.0, as per FN 0039. Beware
142
142
that enabling this option will change the configuration you're loading through NAPALM. Default: ``False`` (won't change your configuration commands).
143
143
.. versionadded:: 3.0.1
144
+
* :code:`force_cfg_session_invalid` (eos) - Force the config_session to be cleared in case of issues, like `discard_config` failure. (default: ``False``)
0 commit comments