Example Programs

cancel
Showing results for 
Search instead for 
Did you mean: 

Parallel Testing with Auto Scheduling NI TestStand Demo

Overview

Note: A similar example is now available with TestStand: TestStand Shipping Example: Parallel Test Strategies Demo

 

This is a software-only demo that illustrates the benefits of testing multiple units under test (UUTs) simultaneously using one set of shared instruments.  The example performs the same set of tests on four units using a sequential, parallel, and auto-scheduled approach, then displays a comparison of the total test time for each approach.

Description

The demo demonstrates testing four Android smart phones using NI TestStand. Four different tests are run on each phone:

  • Power consumption test
  • GPS test
  • Audio quality test
  • Video quality test

These tests are all simulated in software, but in a real-world application, each would utilize a different test instrument.  For this reason, a particular test may only be run on one unit at any given time since the same instrument is required to run a particular test on each UUT.

 

This example demonstrates the following approaches for testing:

 

  1. Sequential Testing.  Each phone is tested sequentially. This is the simplest approach, but it takes the longest amount of time. Since each instrument runs only one of the four tests, each test instrument is left unused while the other tests are executing. Rather than being idle, these instruments could be used to test one of the other phones.
  2. Parallel Testing.  The phones are tested simultaneously, each running in a separate TestStand execution. This approach uses the parallel process model to automatically handle the creation and management of these executions. This approach yields a performance improvement over testing sequentially. However, because of the shared instruments, we observe a pipeline effect: since all tests are executing in the same order, each test socket sits idle until the previous execution is done using each instrument.
  3. Auto Scheduled Testing.  The four phones are tested in parallel using the auto schedule feature of TestStand, which changes the ordering of the test steps to optimize instrument usage.  The Auto schedule step defines multiple test sections which may be executed in any order.  After a section is complete, TestStand finds another section that can be executed based on instrument usage.  

screenshot_20120123131805.png

Hardware and Software Requirements

Parallel Testing Demo - TS2012

TestStand 2012 SP1 or compatible (Free Evaluation)

LabVIEW 2011 or compatible (Free Evaluation)

Parallel Testing Demo - TS2010

TestStand 2010 or compatible

LabVIEW 2011 or compatible

Note: a video of the demo is also available for download to view the example without the required software.

Steps to Implement or Execute Code

  1. Extract the contents of the attached archive.  Open the User Interfaces/NI Mobile Devices Parallel Test User Interface (Small).vi to launch the example User Interface
  2. Run the user interface VI
  3. Click OK when prompted to log in
  4. Click the Single Pass button to launch the demo.
Al B.
Staff Software Engineer - TestStand
CTA/CLD
Contributors