Frequently Asked Questions

For any additional questions please contact Testeract Engineers using the form below.

‍-What is included in TestPoint, the complete Testeract Framework?

A: TestPoint, the Testeract Automated Test Framework, consists of the HAL (Hardware Abstraction Layer), NI TestStand with special plugins, and TASC, the single user experience that takes all of the GUIs and puts them in the same application space.

‍

-Can I use TestPoint if I don’t want to use NI TestStand?

A: Yes, there is some special functionality that NI TestStand offers that works well with TestPoint but you can still use the HAL and TASC without TestStand.

‍

-What is the license cost for TestPoint?

A: Click here to contact Testeract about pricing.

‍

-How does the licensing work?

A: Current licenses are perpetual. For use in individual companies, you can deploy as many deployment versions as you need. For system integrators deploying on other systems, contact us to discuss.

‍

-What is the source code for TestPoint written in?

A: TestPoint is currently written in LabVIEW and requires the LabVIEW Runtime engine (a free download from ni.com) to run.

‍

-Can I get the source code for TestPoint?

A: The source code for parts of TestPoint is available. Except in special cases, the source code for record/playback, the debug GUI, and the logger are not available. If you have a special case, then please contact us to discuss it.

‍

-How can I see what is going on when TestPoint is running?

A: To see what is happening in any given test, you can use the logger or you can create a TestStand UI using LabVIEW that can give you insight into what is happening in real time.

‍

-What is a TASC mode?

A: A mode is a self-contained UI that can plugin to TASC. You use it to create special configurations you would like to have in TASC.

‍

-How many instruments are currently in the HAL?

A: At this time, the HAL has over 9000 instruments.  Click for the link to the current x86 instruments.  Click for the link to the current x64 instruments.

‍

-How hard is it to add instruments to the HAL if they are not already included?

A: There is a defined process for adding instruments. You can add them yourself using the defined process or you can have Testeract Engineers can add them. The difficulty and required time investment will depend on the complexity.

‍

-What is the adoption process for TestPoint?

A: Testeract offers training for TestPoint that takes 3-5 weeks for individual engineers using the framework. Each component takes about a week (HAL, TestStand, and TASC) if you are rushing but 5 weeks is ideal. Additionally, we have a corporate adoption checklist that we go through for each implementation.

‍

-Do I have to know the Actor Framework to use TestPoint?

A: No, you do not need to know the Actor Framework but it is helpful.  Although some parts of TASC, a component of TestPoint, are built in the Actor Framework, Testeract has abstracted it away from normal development.

‍

-How is the HAL different from the HAL that I use?

A: To help you thoroughly evaluate your in-house HAL, Testeract offers an onsite/virtual framework and HAL audit. If you would like to look into getting your HAL evaluated, contact us for details. We find that most in-house HALs do not have as many instruments and do not have special features such as error handling, report generation, hardware simulation, and logging. The Testeract HAL has all of these features with the addition of the ability to include the DUT(Device under test) as part of the HAL which gives you greater flexibility in your system.

‍

-How does TestPoint work with HIL?

A: TestPoint treats HIL like an instrument in the HAL and lets you call into it. Treating it as another instrument greatly simplifies HIL because it treats it as just another piece of hardware with a bus and protocol that we talk to. Contact one of our engineers to discuss this further.

‍

-What types of debug options do you have for TestPoint?

A: As part TestPoint, some of the primary debugging tools we offer are the HAL Debug GUI, logging, and record and playback. With TestPoint, you can look at the logs for a single instrument using the logger and can recreate scenarios you want to test using record and playback.

‍

-How is my automated test framework different from TestPoint?

A: Many companies have developed their own automated test framework. Some are very good and some are less than optimal. To determine how your framework measures up, Testeract offers an assessment where our engineers evaluate it against the requirements you have for your test system. Contact us at Testeract to discuss how we can assess your framework.