moved router list api specs to the testing section

README.md

@@ -354,20 +354,7 @@ Any non-empty responses are JSON formatted messages.
   from the external inventory system, status information is retrieved from the
   alarms database
 
-* /classifier/infinera-dna-addresses, /classifier/juniper-server-addresses
 
-  Both of these resources return lists of source addresses
-  of known senders of snmp traps.  Responses will be
-  formatted as follows:
-
-    ```json
-    {
-        "$schema": "http://json-schema.org/draft-07/schema#",
-        "type": "array",
-        "items": {"type": "string"}
-    }
-    ```
-    
 * /classifier/*`type`*/*`source-equipment`*/*`source-interface`*
 
   The source-equipment is the equipment that causes the trap, not the NMS that
@@ -426,11 +413,30 @@ Any non-empty responses are JSON formatted messages.
     ```
 
 
+### Testing utilities
+
+The following routes are only available if the server
+was started with the `ENABLE_TESTING_ROUTES` flag.
+
+
 * `/testing/flushdb`
 
   This method erases all data in the backend redis
-  data bases and is only available if the server was
-  started with the `ENABLE_TESTING_ROUTES` flag.
+  database.
+
+*  /testing/infinera-dna-addresses, /testing/coriant-tnmp-addresses, /testing/juniper-server-addresses`
+
+  All of these resources return lists of source addresses
+  of known senders of snmp traps.  Responses will be
+  formatted as follows:
+
+    ```json
+    {
+        "$schema": "http://json-schema.org/draft-07/schema#",
+        "type": "array",
+        "items": {"type": "string"}
+    }
+    ```
 
 
 ## Backend (Redis) Storage Schema