Search NASA⌕ Search

SEARCH · Search NASA

Results for “Unit testing”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records

The Structural Evaluation Test Unit (SETU) Benchmark Test Results

A series of extensively instrumented tests was performed on the Structural Evaluation Test Unit in the early 1990s. The purpose of these tests was to determine the response of a minimally designed cask to impacts that were more severe than the design basis impact. This test series provides an excellent opportunity for benchmarking explicit dynamic finite element analysis programs for behaviors that may be experienced by casks during regulatory and extra-regulatory impact events. This report provides the results of the four tests that were conducted. It is meant to go along with a companion report that defines the benchmark problem and gives the locations for the instrumentation and inspection points.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

High Power Alternator Test Unit (ATU) Electrical System Test

The Alternator Test Unit (ATU) in the Lunar Power System Facility (LPSF) located at the NASA Glenn Research Center (GRC) in Cleveland, OH was used to simulate the operating conditions and evaluate the performance of the ATU and it s interaction with various LPSF components in accordance with the JIMO AC Power System Requirements. The testing was carried out at the breadboard development level. Results of these tests will be used for the development and validation of analytical models for performance and lifetime prediction.

Birchenough, Arthur↗

Unit Testing for the Application Control Language (ACL) Software

In the software development process, code needs to be tested before it can be packaged for release in order to make sure the program actually does what it says is supposed to happen as well as to check how the program deals with errors and edge cases (such as negative or very large numbers). One of the major parts of the testing process is unit testing, where you test specific units of the code to make sure each individual part of the code works. This project is about unit testing many different components of the ACL software and fixing any errors encountered. To do this, mocks of other objects need to be created and every line of code needs to be exercised to make sure every case is accounted for. Mocks are important to make because it gives direct control of the environment the unit lives in instead of attempting to work with the entire program. This makes it easier to achieve the second goal of exercising every line of code.

Computer Programming Integrity↗

Test report: Vibration testing of the electron/proton spectrometer structural test unit

The structural test unit of the electron-proton spectrometer was tested to a random vibration spectra and to a sinusoidal resonant search to comply with the requirements of a verification plan for the spectrometer. The test item consisted of mass simulated electronic and printed circuit boards mounted in a flight type electronic housing. The arrangement, center of gravity, and weight were as proposed for flight units.

Vincent, D. L.↗

Test report: Shock test of the electron/proton spectrometer structural test unit

A shock test of the electron-proton spectrometer structural test unit was conducted. The purpose of the shock test was to verify the structural integrity of the electron-spectrometer design and to obtain data on the shock response of the electronics and electronic housing. The test equipment is described and typical shock response data are provided.

Vincent, D. L.↗

Quick setup of unit test for accelerator controls system

Testing a single hardware unit of an accelerator control system often requires the setup of a program with graphical user interface. Developing a dedicated application for a specific hardware unit test could be time consuming and the application may become obsolete after the unit tests. This paper documents a methodology for quick design and setup of an interface focused on performing unit tests of accelerator equipment with minimum programming work. The method has three components. The first is a generic accelerator device object (ADO) manager which can be used to setup, store, and log testing controls parameters for any unit testing system. The second involves the design of a TAPE (Tool for Automated Procedure Execution) sequence file that specifies and implements all te testing and control logic. The sting third is the design of a PET (parameter editing tool) page that provides the unit tester with all the necessary control parameters required for testing. This approach has been used for testing the horizontal plane of the Stochastic Cooling Motion Control System at RHIC.

43 PARTICLE ACCELERATORS↗

Unit Testing for Command and Control Systems

Unit tests were created to evaluate the functionality of a Data Generation and Publication tool for a command and control system. These unit tests are developed to constantly evaluate the tool and ensure it functions properly as the command and control system grows in size and scope. Unit tests are a crucial part of testing any software project and are especially instrumental in the development of a command and control system. They save resources, time and costs associated with testing, and catch issues before they become increasingly difficult and costly. The unit tests produced for the Data Generation and Publication tool to be used in a command and control system assure the users and stakeholders of its functionality and offer assurances which are vital in the launching of spacecraft safely.

testing↗

Adventures in cFS Unit Testing: Examining the Past to Explain the Present with an Eye toward the Future

An overview of my experiences writing unit tests for various projects with a specific focus on my work unit testing core Flight System (cFS) applications. I recount some of the direct personal experiences I have had that showed me the utility of having done unit testing for my projects. Many of the tips, tricks and pitfalls encountered during my time writing unit tests for the cFS app, CF, are examined. I also compare and contrast my cFS unit testing development with that of a parallel project, in which I write unit tests using RSpec, a testing framework for the Ruby programming language. I impart my complete methodology behind the CF app unit testing effort and the rationale for why I did it that way. Then I give some ideas for how you can do your own unit testing for cFS applications. You will also learn about my hopes for how unit testing cFS applications can be done going forward from where we are now.

"unit testing"↗

Architecture-Based Unit Testing of the Flight Software Product Line

This paper presents an analysis of the unit testing approach developed and used by the Core Flight Software (CFS) product line team at the NASA GSFC. The goal of the analysis is to understand, review, and reconunend strategies for improving the existing unit testing infrastructure as well as to capture lessons learned and best practices that can be used by other product line teams for their unit testing. The CFS unit testing framework is designed and implemented as a set of variation points, and thus testing support is built into the product line architecture. The analysis found that the CFS unit testing approach has many practical and good solutions that are worth considering when deciding how to design the testing architecture for a product line, which are documented in this paper along with some suggested innprovennents.

Ganesan, Dharmalingam↗

Design assessment of a 150 kWt CFBC Test Unit

For clean and efficient energy generation from coal, the most suitable technology known to date is 'Fluidized Bed Combustion' technology. Applications of circulating fluidized bed (CFB) combustion technology have been steadily increasing in both capacity and number over the past decade. Designs of these units have been based on the combustion tests carried out in pilot scale facilities to determine the combustion and desulfurization characteristics of coal and limestone reserves in CFB conditions. Similarly, utilization of Turkish lignites in CFB boilers necessitates adaptation of CFB combustion technology to these resources. However, the design of these test units are not based on firing coals with high ash, volatile matter and sulfur contents like Turkish lignites. For this purpose, a 150 kWt CFB combustor test unit is designed and constructed in Chemical Engineering Department of Middle East Technical University, based on the extensive experience acquired at the existing 0.3 MWt Bubbling Atmospheric Fluidized Bed Combustor (AFBC) Test Rig. Following the commissioning tests, a combustion test is carried out for investigation of combustion characteristics of Can lignite in CFB conditions and for assessment of the design of test unit. Comparison of the design outputs with experimental results reveals that most of the predictions and assumptions have acceptable agreement with the operating conditions. In conclusion, the performance of 150 kWt CFBC Test Unit is found to be satisfactory to be utilized for the long term research studies on combustion and desulfurization characteristics of indigenous lignite reserves in circulating fluidized bed combustors. (author)

01 COAL, LIGNITE, AND PEAT↗

Requirements document for mini system test unit

The mini system test unit (STU) for the Trace Gas Analyzer (TGA) is defined. The interface signals of the components used to implement the STU are also defined. The mini STU is used to support pre-flight ground test operations. The STU indications of TGA operation (organic and carbon monoxide analyses) and its ability to monitor gas chromatograph and mass spectrometer test signals are included.

Garofolo, D.↗

The Structural Evaluation Test Unit (SETU) Benchmark Problem Statement

A series of extensively instrumented tests was performed on the Structural Evaluation Test Unit in the early 1990s. The purpose of these tests was to determine the response of a minimally designed cask to impacts that were more severe than the design basis impact. This test series provides an excellent opportunity for benchmarking explicit dynamic finite element analysis programs for behaviors that may be experienced by casks during regulatory and extra-regulatory impact events. This report provides the parameters of the test unit, the locations of instrumentation, the locations of inspection points, and the parameters of the four tests that were conducted. A companion report provides the results of the tests.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Unit Testing and Remote Display Development

The Kennedy Space Center is currently undergoing an extremely interesting transitional phase. The final Space Shuttle mission, STS-135, was completed in July of 2011. NASA is now approaching a new era of space exploration. The development of the Orion Multi- Purpose Crew Vehicle (MPCV) and the Space Launch System (SLS) launch vehicle that will launch the Orion are currently in progress. An important part of this transition involves replacing the Launch Processing System (LPS) which was previously used to process and launch Space Shuttles and their associated hardware. NASA is creating the Spaceport Command and Control System (SCCS) to replace the LPS. The SCCS will be much simpler to maintain and improve during the lifetime of the spaceflight program that it will support. The Launch Control System (LCS) is a portion of the SCCS that will be responsible for launching the rockets and spacecraft. The Integrated Launch Operations Applications (ILOA) group of SCCS is responsible for creating displays and scripts, both remote and local, that will be used to monitor and control hardware and systems needed to launch a spacecraft. It is crucial that the software contained within be thoroughly tested to ensure that it functions as intended. Unit tests must be written in Application Control Language (ACL), the scripting language used by LCS. These unit tests must ensure complete code coverage to safely guarantee there are no bugs or any kind of issue with the software.

LCS↗