September 14, 2010

TestTrack SDK Expert Series Webinar Recording: Getting Started With the TestTrack SDK

Helix ALM
Thanks to everyone who joined us for the Getting Started With the TestTrack SDK webinar. The recording is now available if you missed the webinar or want to watch it again. Q&A from the session is below. The next session, Extending and Automating the TestTrack SDK is scheduled for September 29. If you're already registered for the series, you'll receive the meeting information in the next few days. We had some issues with on-screen visibility of Jeff's code samples during this event, which are being worked out. We don't expect to have the same issues in the next session. You can download the slides and sample code from this webinar.

Download video in mp4 format


1. How is the TestTrack SDK licensed? Are the licenses named or floating? Every TestTrack license contains client access license based on its type (floating or named) plus a floating license for SOAP access. Read more about TestTrack SOAP licensing. 2. What is the difference between defect number and defect recordID? Defect numbers can be changed but recordID is an internal ID for the defect record and cannot be changed.  The two are not connected, recordID increments from one at project creation while defect numbers can be changed at anytime by a user with the proper permissions. This also applies to requirement, test case, and test run numbers and recordIDs. 3. Is there an option to add users to the Seapine Licence Server (LDAP users) through SOAP? Not through the TestTrack SOAP API. The License Server has its own API with that functionality. The License Server Admin Guide includes information about the API. 4. Are there pre-built scripts available for having one TestTrack project talk to another TestTrack project? Yes, the Defect Mover sample includes code and logic to move defects between TestTrack projects. 5. If the audit log is turned on, who is the user responsible for the changes made? Is it SOAP User? The audit trail will report that the change was made through SOAP and attribute the change to the user that you used in the log on method. This is another reason to use a dedicated user for SOAP activities, improved traceability to the user that made the change. 6. Are there other sample scripts available as a reference? Yes, there are TestTrack SOAP tutorials for a variety of languages as well as working TestTrack SOAP samples available in The Seapine View. 7. I'm looking for help with a reporting tool like BIRT or Crystal Reports? The SOAP API can run TestTrack reports, but it's not meant as a reporting interface. To integrate a third-party reporting package with TestTrack, check out the TestTrack reporting plug-ins.