Search NASA⌕ Search

SEARCH · Search NASA

Results for “Automated Functional 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
All sourcesNASA NTRSDOE OSTI
DOE OSTI2026

A Scalable Test-Bed for Direct Current Current Transformer Automated Functional Testing and Characterization

This article describes a scalable test-bed for automation of measurements of the direct current current transformers (DCCT). Automation of measurement involves functional measurements, fault event based measurements and data validation. The test-bed is designed to measure up to 20 DCCTs at a time with software based measurement repetition checks and validation of the measurements.

43 PARTICLE ACCELERATORS↗
DOE OSTI2024

Maximizing Efficiency and Quality: Leveraging Automated Testing for Laboratory Commissioning

The traditional commissioning process uses sampling to select equipment for functional acceptance testing when large quantities of equipment are present. Although this approach is generally effective in identifying wide-spread issues, it has several shortcomings: it fails to evaluate equipment not included in the sample, provides only a one-time validation of equipment operation, and the standard documentation is a simple checklist of pass/fail questions. During the construction and commissioning process of the new Research and Innovation Laboratory (RAIL) in Golden, CO, the National Renewable Energy Laboratory team engaged Group14 Engineering to implement a Connected Commissioning process using fault detection and diagnostic software for automated functional acceptance testing. This presentation highlights the advantages offered by automated functional testing in this critical laboratory setting: (1) sampling 100% of BAS-connected equipment during functional testing, (2) testing results backed by data beyond the traditional pass/fail checklist, and (3) an automated test process that can be regularly executed by the building management team for ongoing commissioning throughout the life of the building. The presentation will also cover technical challenges associated with Connected Commissioning and the important conversations with key stakeholders that need to occur well before functional acceptance testing in order to successfully implement the automated testing processes.

automated testing↗
NASA NTRS2005

Comparison of Cognitive Performance Tests for Promethazine Pharmacodynamics in Human Subjects

The objective of this study is to compare cognitive function tests, Automated Neurological Assessment Metrics (ANAM) based Readiness Evaluation System (ARES(Registered TradeMark)) on a Palm Pilot and Windows based Spaceflight Cognitive Assessment Tool (WinSCAT(Registered TradeMark)) on a personal computer (PC) to assess performance effects of promethazine (PMZ) after administration to human subjects. In a randomized placebo-controlled cross-over design, subjects received 12.5, 25, and 50 mg intramuscular (IM) PMZ or a placebo and completed 14 sessions with WinSCAT(Registered TradeMark) (v. 1.26) and ARES(Registered TradeMark) (v. 1.27) consecutively for 72 h post dose. Maximum plasma concentrations (4.25, 6.25 and 13.33 ng/ml) were linear with dose and were achieved by 0.75, 8, and 24 h after dosing for the three doses, respectively. No significant differences in cognitive function after PMZ dosing were detected using WinSCAT(Registered TradeMark), however, tests from ARES(Registered TradeMark) demonstrated concentration dependent decrements in reaction time associated with PMZ dose.

Vaksman, Z.↗
DOE OSTI2023

Maximizing Efficiency and Quality: Leveraging Automated Testing for Laboratory Commissioning

The traditional commissioning process for a building often implements sampling rates to select equipment for functional acceptance testing when large quantities of equipment are present. While this approach is generally effective in identifying wide-spread issues, it has several key shortfalls. (1) It provides a one-time validation of equipment operation in which the standard documentation is a simple checklist of pass/fail questions. (2) It fails to evaluate equipment not included in the sample rate selection. During the construction and commissioning process of the new Research and Innovation Laboratory (RAIL) in Golden, CO, the National Renewable Energy Laboratory team engaged Group14 Engineering to implement a Connected Commissioning process using fault detection and diagnostic software for automated functional acceptance testing. The goal of this presentation will be to highlight the advantages offered by automated functional testing in this critical laboratory setting. These are primarily (1) sampling 100% of BAS-connected equipment during functional testing, (2) testing results backed by data beyond the traditional pass/fail checklist, and (3) an automated test process that can be regularly executed by the building management team for ongoing commissioning throughout the life of the building. The presentation will also cover technical challenges associated with connected commissioning and the important conversations with the key stakeholders that need to occur well before functional acceptance testing in order to successfully implement the automated testing processes.

automated testing↗
NASA NTRS1974

An automated system for pulmonary function testing

An experiment to quantitate pulmonary function was accepted for the space shuttle concept verification test. The single breath maneuver and the nitrogen washout are combined to reduce the test time. Parameters are defined from the forced vital capacity maneuvers. A spirometer measures the breath volume and a magnetic section mass spectrometer provides definition of gas composition. Mass spectrometer and spirometer data are analyzed by a PDP-81 digital computer.

Mauldin, D. G.↗
DOE OSTI2022

Experimental testing of a control barrier function on an automated vehicle in live multi-lane traffic

This paper experimentally tests an implementation of a control barrier function (CBF) designed to guarantee a minimum time-gap in car following on an automated vehicle (AV) in live traffic, with a majority occurring on freeways. The CBF supervises a nominal unsafe PID controller on the AV’s velocity. The experimental testing spans two months of driving, of which 1.9 hours of data is collected in which the CBF and nominal controller are active. We find that violations of the guaranteed minimum time-gap are observed, as measured by the vehicle’s on-board radar unit. There are two distinct causes of the violations. First, in multi-lane traffic, Cut-ins from other vehicles represent external disturbances that can immediately violate the minimum guaranteed time gap provided by the CBF. When cut-ins occur, the CBF does eventually return the vehicle to a safe time gap. Second, even when cut-ins do not occur, system model inaccuracies (e.g., sensor error and delay, actuator error and delay) can lead to violations of the minimum time-gap. These violations are small relative to the violations that would have occurred using only the unsafe nominal control law.

99 GENERAL AND MISCELLANEOUS↗
NASA NTRS1976

An automated miniaturized Haploscope for testing binocular visual function

A computer-controlled binocular vision testing device has been developed as one part of a system designed for NASA to test the vision of astronauts during spaceflight. The device, called the Mark III Haploscope, utilizes semi-automated psychophysical test procedures to measure visual acuity, stereopsis, phorias, fixation disparity and accommodation/convergence relationships. All tests are self-administered, yield quantitative data and may be used repeatedly without subject memorization. Future applications of this programmable, compact device include its use as a clinical instrument to perform routine eye examinations or vision screening, and as a research tool to examine the effects of environment or work-cycle upon visual function.

Decker, T. A.↗
NASA NTRS2018

Robots and Robots and More

Over the course of this year I worked on several projects across different departments, from physical robots at Swamp Works, to automated robots running functional tests on launch critical Graphical User Interfaces (GUIs). My overarching project this year was designing a new automated testing framework. It began with becoming familiar with the existing automated testing framework, which used image matching to perform programmatic GUI testing. After writing a few dozen tests with the existing framework, I was able to identify the strengths and weaknesses of the system and begin the search for another tool to replace it. I ended up selecting an open source library, which I modified to fit both National Aeronautics and Space Administration (NASA) requirements and those of the specific Computer Software Configuration Item (CSCI) I worked on. After the new framework was feature-rich enough to meet the team requirements, I helped roll out the changes, managed the transition to the new framework, and directed continuing automation work in regards to the library. The result was a comprehensive new way of efficiently testing the GUI that was robust enough to handle small changes to the GUI itself. Additionally, for approximately six weeks I worked on rebuilding, repairing, and updating the software of four "Swarmie" robots for a NASA event. By the close of the six weeks, the four robots were operational and had improved obstacle detection software that solved a faulty stop signal issue that the robots were experiencing.

Siegel, Alex↗
NASA NTRS1988

Artificial intelligence in a mission operations and satellite test environment

A Generic Mission Operations System using Expert System technology to demonstrate the potential of Artificial Intelligence (AI) automated monitor and control functions in a Mission Operations and Satellite Test environment will be developed at the National Aeronautics and Space Administration (NASA) Jet Propulsion Laboratory (JPL). Expert system techniques in a real time operation environment are being studied and applied to science and engineering data processing. Advanced decommutation schemes and intelligent display technology will be examined to develop imaginative improvements in rapid interpretation and distribution of information. The Generic Payload Operations Control Center (GPOCC) will demonstrate improved data handling accuracy, flexibility, and responsiveness in a complex mission environment. The ultimate goal is to automate repetitious mission operations, instrument, and satellite test functions by the applications of expert system technology and artificial intelligence resources and to enhance the level of man-machine sophistication.

Busse, Carl↗
NASA NTRS1990

Automation of Space Station module power management and distribution system

Viewgraphs on automation of space station module (SSM) power management and distribution (PMAD) system are presented. Topics covered include: reasons for power system automation; SSM/PMAD approach to automation; SSM/PMAD test bed; SSM/PMAD topology; functional partitioning; SSM/PMAD control; rack level autonomy; FRAMES AI system; and future technology needs for power system automation.

Bechtel, Robert↗
NASA NTRS2017

Launch Control System Software Development System Automation Testing

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This system requires high quality testing that will measure and test the capabilities of the system. For the past two years, the Exploration and Operations Division at Kennedy Space Center (KSC) has assigned a group including interns and full-time engineers to develop automated tests to save the project time and money. The team worked on automating the testing process for the SCCS GUI that would use streamed simulated data from the testing servers to produce data, plots, statuses, etc. to the GUI. The software used to develop automated tests included an automated testing framework and an automation library. The automated testing framework has a tabular-style syntax, which means the functionality of a line of code must have the appropriate number of tabs for the line to function as intended. The header section contains either paths to custom resources or the names of libraries being used. The automation library contains functionality to automate anything that appears on a desired screen with the use of image recognition software to detect and control GUI components. The data section contains any data values strictly created for the current testing file. The body section holds the tests that are being run. The function section can include any number of functions that may be used by the current testing file or any other file that resources it. The resources and body section are required for all test files; the data and function sections can be left empty if the data values and functions being used are from a resourced library or another file. To help equip the automation team with better tools, the Project Lead of the Automated Testing Team, Jason Kapusta, assigned the task to install and train an optical character recognition (OCR) tool to Brandon Echols, a fellow intern, and I. The purpose of the OCR tool is to analyze an image and find the coordinates of any group of text. Some issues that arose while installing the OCR tool included the absence of certain libraries needed to train the tool and an outdated software version. We eventually resolved the issues and successfully installed the OCR tool. Training the tool required many images and different fonts and sizes, but in the end the tool learned to accurately decipher the text in the images and their coordinates. The OCR tool produced a file that contained significant metadata for each section of text, but only the text and coordinates of the text was required for our purpose. The team made a script to parse the information we wanted from the OCR file to a different file that would be used by automation functions within the automated framework. Since a majority of development and testing for the automated test cases for the GUI in question has been done using live simulated data on the workstations at the Launch Control Center (LCC), a large amount of progress has been made. As of this writing, about 60% of all of automated testing has been implemented. Additionally, the OCR tool will help make our automated tests more robust due to the tool's text recognition being highly scalable to different text fonts and text sizes. Soon we will have the whole test system automated, allowing for more full-time engineers working on development projects.

Automation↗
NASA NTRS1986

Software testing - A way to improve software reliability

Various software testing techniques are described. The techniques are classified as dynamic or static, structural or functional, and manual or automated. The objects tested include the elements designed during the development of the software, such as codes, data structures, and requirements. Testing techniques and procedures applicable to each phase of software development are examined; the development phases are: software requirements analysis, preliminary design, detailed design, coding, testing, and operation and maintenance. The characteristics of a future software engineering environment for software testing and validation are discussed.

Mahindru, Andy↗
NASA NTRS2017

Software Verification of Orion Cockpit Displays

NASA's latest spacecraft Orion is in the development process of taking humans deeper into space. Orion is equipped with three main displays to monitor and control the spacecraft. To ensure the software behind the glass displays operates without faults, rigorous testing is needed. To conduct such testing, the Rapid Prototyping Lab at NASA's Johnson Space Center along with the University of Texas at Tyler employed a software verification tool, EggPlant Functional by TestPlant. It is an image based test automation tool that allows users to create scripts to verify the functionality within a program. A set of edge key framework and Common EggPlant Functions were developed to enable creation of scripts in an efficient fashion. This framework standardized the way to code and to simulate user inputs in the verification process. Moreover, the Common EggPlant Functions can be used repeatedly in verification of different displays.

Biswas, M. A. Rafe↗
NASA NTRS2016

Automation of Flight Software Regression Testing

NASA is developing the Space Launch System (SLS) to be a heavy lift launch vehicle supporting human and scientific exploration beyond earth orbit. SLS will have a common core stage, an upper stage, and different permutations of boosters and fairings to perform various crewed or cargo missions. Marshall Space Flight Center (MSFC) is writing the Flight Software (FSW) that will operate the SLS launch vehicle. The FSW is developed in an incremental manner based on "Agile" software techniques. As the FSW is incrementally developed, testing the functionality of the code needs to be performed continually to ensure that the integrity of the software is maintained. Manually testing the functionality on an ever-growing set of requirements and features is not an efficient solution and therefore needs to be done automatically to ensure testing is comprehensive. To support test automation, a framework for a regression test harness has been developed and used on SLS FSW. The test harness provides a modular design approach that can compile or read in the required information specified by the developer of the test. The modularity provides independence between groups of tests and the ability to add and remove tests without disturbing others. This provides the SLS FSW team a time saving feature that is essential to meeting SLS Program technical and programmatic requirements. During development of SLS FSW, this technique has proved to be a useful tool to ensure all requirements have been tested, and that desired functionality is maintained, as changes occur. It also provides a mechanism for developers to check functionality of the code that they have developed. With this system, automation of regression testing is accomplished through a scheduling tool and/or commit hooks. Key advantages of this test harness capability includes execution support for multiple independent test cases, the ability for developers to specify precisely what they are testing and how, the ability to add automation, and the ability of the harness and cases to be executed continually. This test concept is an approach that can be adapted to support other projects.

Tashakkor, Scott B.↗