August 12, 2009
TestTrack SDK Helpful Hint - Troubleshooting
In this installment of the TestTrack SDK Helpful Hint posts, I am going to discuss ways to troubleshoot issues when programming with the SOAP SDK.
Basic Programming TipsIf you are using the TestTrack SDK, chances are that you have some familiarity with programming, so the following list is probably nothing new to you:
- Run in Debug mode: If you are in an Integrated Development Environment, chances are you have the ability to use breakpoints and run the application in Debug mode. With the TestTrack SDK, you could see how a CDefect object is being built, like the array of CEvents used in the workflow.
- Print out to console: If you are not in an Integrated Development Environment and do not have access to breakpoints, then you might only be able to print to console the values of variables to make sure everything is being built correctly.
- Keep it simple: Start simple and build up until you run into the issue. For example, let's say you are writing an application that logs in to TestTrack, gets a list of defects based on field values, gets a number of them for modification, and then logs out. When you run the application you get exceptions. So where is the problem? Break it down. First, write a simple application that logs in and out of TestTrack. Did that cause a problem? Then add the code to get the defect list. Did that cause a problem? So you get the idea. You keep building it up until the issue appears again. This should allow you to isolate the issue.