Allan James D.

Elarde ECEA124-2P_E03 CW #1

Test and Development 3

CW #3
STS Exercise 1

Elarde, Allan James D.

ECEA124-3P/E03
2020101939

Prof. Mary Ann Latina

School of Electrical, Electronics, & Computer Engineering, Mapúa University
Allan James D. Elarde ECEA124-2P_E03 CW #1

I. Exercise No. 1

Opening the TestStand 2016 (64-bit) Sequence Editor and logging in as an administrator are
required for the experiment. The user is requested to enter a name and location for the test
program when using the Create STS Project Tool, which can be found in the Tools menu. Based
on the given data, the tool builds the test program template. The paper emphasizes how crucial
it will be to modify the template in the future since it must be customized to the tester
environment and test strategy. It underlines the necessity of expanding the test plan to include
functionality testing for the device under test as well as continuity check and leakage
measurement. The report's conclusion lists the crucial actions that were made during the
exercise and the consequent folder structure of the test program that was produced.

II. Objectives

The main objectives of this exercise are as follows:

 Recognize how to employ the Create STS Project Tool.

 Create a template for a high-level test program for an STS project.
 Get acquainted with the created test program's file structure and organization.
 Discover how to save the developed test program and examine it in the TestStand
Sequence Editor.
 Determine the test program's primary sequences and step groups.
 Become more knowledgeable about the function and intent of the ProcessSetup,
MainSequence, and ProcessCleanup sequences.
 Discover the Code Modules, Limits, and Supporting Materials folders in the tool's built
folder structure.
 Recognize the necessity for future adjustments to the test program in order to match
the particular tester configuration and test plan.
Allan James D. Elarde ECEA124-2P_E03 CW #1

III. Discussion

A critical step in designing an efficient testing solution for a Device Under Test (DUT) inside an
STS environment is the creation of a test program using the Create STS Project Tool. We may
further analyze the importance and ramifications of using this tool by scrutinizing the goals and
execution procedures described in this report.

The Create STS Project Tool's capacity to simplify initial setup of a test program is one of its main
benefits. The application avoids the need to start from scratch and offers a consistent structure
for arranging test sequences and resources by providing a high-level test program template. This
helps an organization's many test programs run consistently while also saving time.

The created test program template acts as a foundation for future development and
modification. Future adjustments are required, as stated in the report, to customize the test
program to the unique requirements of the DUT, tester setup, and test plan. These adjustments
might involve adding or changing test stages, introducing more instrumentation, setting test
constraints, or including certain functionality tests.

The created test program's file structure is intended to improve organization and
maintainability. The Code Modules folder enables modular and reusable code components,
fostering effective test program creation and maintenance. To make it simpler to maintain and
adjust test limits and thresholds as needed, the Limits folder offers a central location for their
definition. It is possible to put pertinent documentation, diagrams, or other supporting materials
in the Supporting Materials folder. Users obtain a greater grasp of the test flow and logic by
investigating the sequences and step groups inside the test program. Initializing tester resources
and setting up the testing environment are handled by the ProcessSetup sequence. The main
loop for testing the DUT, where tests are run and outcomes are assessed, is contained in the
MainSequence. The ProcessCleanup procedure guarantees that the test system is properly shut
down and cleaned up at the end.
Allan James D. Elarde ECEA124-2P_E03 CW #1

IV. Interpretation of the Output

The exercise's result offers useful knowledge and insights on how to create a test program using
the Create STS Project Tool. Users may efficiently use the tool to create a high-level test
program template by adhering to the suggested instructions. This model may be used as a
starting point for creating a planned and controlled test program.

It is crucial to remember that the test program template provided is not a permanent fix. The
result highlights the need for future adjustments and personalization to match the test program
with particular requirements. These adjustments could involve adding more test stages, setting
up instrumentation, establishing test limits, and putting in place particular functionality tests
made for the Device Under Test (DUT).

comprehension of the rationale and test flow. Initializing tester resources and configuring the
testing environment are handled by the ProcessSetup sequence. The main testing loop, where
tests are run and results are assessed, is contained in the MainSequence. Finally, the
ProcessCleanup routine makes sure that the test system is properly shut down and cleaned up.

The output also emphasizes how crucial the organization and file structure are inside the
created test program. Modular and reusable code components are supported by the Code
Modules folder, allowing for effective development and upkeep. While the Supporting Materials
folder can include pertinent material and resources for reference, the Limits folder offers a
consolidated area for controlling test limits.

V. Key Learnings

 A useful tool for creating a high-level test program template in an STS environment is
the Create STS Project Tool.
Allan James D. Elarde ECEA124-2P_E03 CW #1

 A customized test program may be created using the supplied test program template as
a structured starting point.
 The test program template will need to be modified in the future to accommodate
different tester settings, test strategies, and Device Under Test (DUT) needs.
 Gaining an understanding of the test program's sequences and step groups, such as
ProcessSetup, MainSequence, and ProcessCleanup, facilitates comprehension of the
logic and overall test flow.
 Maintainability and reusability of the test program are facilitated by the test program's
file structure and organization, which includes the Code Modules, Limits, and Supporting
Materials folders.
 The test program template must be improved and refined through iterative
development in order to satisfy the unique testing requirements.
 The Create STS Project Tool streamlines initial setup, saves time, and encourages
uniformity among test programs.
 The test program template may be altered to incorporate further test stages, set up
instrumentation, specify test limitations, and carry out particular functionality tests for
the DUT.
 A well-structured and simple to manage test program benefits from proper
documentation and arrangement of supporting resources.
 The Create STS Project Tool's knowledge may be used for a variety of projects and
testing situations inside the STS environment.
Allan James D. Elarde ECEA124-2P_E03 CW #1