Hi Mohamed,

You should be unit testing only the code you've written, and based on your post I don't think you've written any code in this particular case. If you are using just the protocol.xml, you can just rely on it working as expected. What you could do is some QA work, in order to make sure you've implemented everything correctly.

I this case I don't think unit testing makes sense unless you wrote some QActions as well, did you?

Cheers

Hi,

As Edib mentioned, unit tests are meant to ensure that small parts of your code do what is expected. This makes it easier to pinpoint the problem in a complex solution in case something goes wrong.

Since your SNMP connector consists mostly of polling and possibly a few actions on the XML side, it is not very suitable for unit testing.

Apart from Edib's suggestion of a thorough QA process, you could look into Integration Testing or Regression Testing, which would be similar to what we do at Skyline when we test the entire software.

You could either via connection with a real device or an SNMP simulation have a testing element created on your Development/Staging/QA environment and then use something like an automation script that goes and reads certain parameters from the element and verifies they contain the expected value.

This typically is a more complex process but if you would really like to have automated testing for your new connector then it is something you can look into.