ADE (MTB) IKP-4198 development documentation.

List of tests to be completed for (MTB) ADE before delivering a feature.

List of tests:

Test the parser script with data collected from a similar machine/ appliance/chassis for the command being run in the .ind.yaml file created for the parser to check the output data is parsed correctly.
Test the parser script with Data collected from the customer to ensue the outputs match the data received for the command being run the .ind.yaml file created for the parser to check the output data is parsed correctly.
Alert a simulation on a live device to ensure the correct alert is generated for metric being tested by the rule.
Modify and verify the issue items(vs id, cpu number etc.) are being displayed correctly when the alert is generated.
Complete the command-runner tests for the .ind.yaml scripts to rule out any potential bugs in the script.

The .ind.yaml file has been completed with the information for the parser.
The parser .py has been completed to extract the vs.id, concurrent connections as well as throughput per VS per chassis.
Tests using a live Lab device as on indeni server has been completed.
unit tests using the mock devices has been completed successfully.

Need to add additional tags for vs.name and will need to add additional command to get the name also displayed.
Need to get the alert generated for concurrent connections nearing peak.
Change the name of folders and unit tests to match the standard naming formats.
Get the information from Charles explicitly that no alert is required for throughput
After the all the tests are finished. Write the parser using the textfsm.
commit the code with the changes done using standard python parsing as well as latter with textfsm.