Advancing HL7 v2 to New Heights: A Platform for Developing Specifications, Test Plans, and Testing Tools

The web has a lot of sites devoted to testing and test tools. If you are in charge of designing a test program for your development, a few hours surfing the sites listed here could get you off to a pretty good start. We'll visit some of the sites that offer test tools, but for the most part, I'm going to focus on sites that talk about testing, test methods, and test plans. There will be plenty of sites that have links to the tools, so you can take off from there. But remember, a test tool is not a test plan.

In software testing process, test data generation represents an important step for high quality software, even for mobile devices. As proposed in previous works, a potential source for random data generation is represented by the UI layout files that are used for almost all mobile platforms (Android, iOS, Windows Phone/Mobile). This paper continues the previous work and presents a test data generation system based on Android layout files. The test data generator uses DSL files as input and generates test data that conform to several testing principles. The generated test data could be stored in XML files or any format required by the testing frameworks.

To explain the common conformance and interoperability testing requirements of eHealth applications through two case studies; one using a prominent eHealth messaging standard, namely HL7 v3 [1], and the other using Integrating the Healthcare Enterprise (IHE) [2] Profiles and to describe how these testing requirements can be addressed through an automated, modular and scenario-based testing framework, namely TestBATN. Summarizing the conformance testing requirements of HL7 v3 messages. Illustrating the interoperability testing requirements of IHE Profiles through a scenario based on the IHE XDS, IHE XDS-MS and IHE PIX profiles. Explaining how these requirements can be handled through a dynamic and configurable test framework addressing all the layers in the interoperability stack within a single test scenario. Conformance and interoperability testing are necessary to maintain correct information exchange as the correctness of the exchanged data is essential in the healthcare domain. There are many standards used in eHealth that the applications need to conform. Additionally, there are profiling initiatives such as IHE and Continua Health Alliance which publish integration profiles addressing a specific clinical need or a use case and describe how to combine or use the existing standards to provide interoperability. However, as the results of our case studies demonstrate, there are many commonalities in the conformance and interoperability testing requirements of these standards and profiles and therefore an integrated testing environment is needed. Our main conclusion is that rather than having individual testing tools for each standard or initiative, a generic and modular test framework exploiting the commonalities in the testing processes and fostering reusability of modular, pluggable testing components will improve the efficiency of testing. Through the TestBATN framework, we describe how this modularity can be achieved by providing common interfaces facilitating the development of adaptors which allows different testing components to be plugged into the system.

Health Level Seven (HL7) is a prominent messaging standard in the eHealth domain, and with HL7 v2, it addresses only the messaging layer. However, HL7 implementations also deal with the other layers of interoperability, namely the business process layer and the communication layer. This need is addressed in HL7 v3 by providing a number of normative transport specification profiles. Furthermore, there are storyboards describing HL7 v3 message choreographies between specific roles in specific events. Having alternative transport protocols and descriptive message choreographies introduces great flexibility in implementing HL7 standards, yet, this brings in the need for test frameworks that can accommodate different protocols and permit the dynamic definition of test scenarios. In this paper, we describe a complete test execution framework for HL7-based systems that provides high-level constructs allowing dynamic set up of test scenarios involving all the layers in the interoperability stack. The computer-interpretable test description language developed offers a configurable system with pluggable adaptors. The Web-based GUIs make it possible to test systems over the Web anytime, anywhere, and with any party willing to do so.

ABSTRACTBalancing consumer's and producer's risk is an important consideration when planning tests. Instead of focusing on finding a single best test plan, we introduce a general framework to systematically identify a set of binomial test plans by leveraging the inverse relationship between the two risks. The framework is applied to compare a variety of assurance testing frameworks, including classical tests, and Bayesian reliability assurance tests such as the Bayesian assurance test, the assurance reliability demonstration test, and the coverage criterion test. Efficient algorithms are presented to compute the set of test plans, providing practitioners with a comprehensive range of options to choose from. In addition, we include a comparison to the sequential probability ratio test. We also provide formal proofs for the inverse relationship between consumer's and producer's risk in Bayesian reliability assurance tests that underlie our algorithms. A case study is presented to illustrate the framework's application and compare the risks associated with different test plans.

Over the years, software development has evolved from being a simple coding activity into a highly organized and structured process that requires the use of a wide variety of tools and techniques. These tools are essential for improving productivity, ensuring accuracy, managing time efficiently, and delivering quality software within deadlines. The purpose of this study is to explore the impact of different tools and techniques used in software projects and how they contribute to the overall success of a project. Software development is no longer limited to just writing code; it involves several critical phases such as requirement gathering, planning, designing, coding, testing, deployment, and maintenance. Each of these phases benefits from specialized tools that simplify tasks, enhance collaboration, reduce errors, and increase overall efficiency. With the growing popularity of agile methodologies and the widespread adoption of DevOps culture, the use of automated tools, project management platforms, testing frameworks, and version control systems has become essential for modern software teams. Selecting the right tools and integrating them effectively into the development process plays a major role in determining whether a project will meet its objectives. This study aims to analyze the significance of these tools in real-world software projects, highlighting their advantages, practical applications, and limitations. The findings of this study will provide valuable insights for developers, project managers, and organizations looking to optimize their software development practices using modern tools and techniques. This research focuses on key areas such as project planning, development life cycle, team collaboration, agile and DevOps practices, version control, and testing tools—all of which contribute to successful and high-quality software delivery. Keywords: software project, software development, tools and techniques, project success, agile methodology, DevOps, software development life cycle, project planning, version control, testing tools, automation, productivity, collaboration, deployment.

: The significance of this research and development lies in the application of the developed simulation tools and techniques to the evaluation of potential Multifunction Inertial Reference Assembly (MIRA) sensor systems. These systems use a minimum number of inertial sensors to provide the inertial-reference information necessary to meet the aircraft requirements for weapon delivery, flight control, navigation, fire control, and flight safety. This contract considers development of real-time operation, and the addition of a navigation and attitude error-propagation algorithm. Other models added to the simulation are two-degree-of-freedom gyros, an air-data system, an autopilot, and a transport vehicle. Parametric studies and evaluations of potential MIRA configurations were conducted to support the definition of the long-term MIRA requirements, and to provide an independent evaluation of candidate configurations. The philosophy and details of a test and development plan, specifically geared to MIRA systems, are also discussed.

Web services (WS) is currently the major implementation of service-oriented architecture (SOA). It defines a framework for agile and flexible integration among autonomous services based on Internet open standards. However, testing has been a challenge due the dynamic and collaborative nature of WS. This paper introduces an on-going project on a multiagent based framework to coordinate distributed test agents to generate, plan, execute, monitor and communicate tests on WS. Test agents are classified into different roles which communicate through XML-based agent test protocols. Test master accepts test cases from test generator, generates test plans and distributed them to various test groups. A set of test agents that implement a test plan are organized into a test group, which is coordinated by a test coordinator. Test runners execute the test scripts, collect test results and forward the results to test analyzer for quality and reliability analysis. The status of the test agents are monitored by the test monitor. Test agents are dynamically created, deployed and organized. Through the monitoring and coordinating mechanism, the agents can re-adjust the test plan and their behavior at runtime to be adaptive to the changing environment.

Testing in the workplace: finding a path through a pandemic

NASA's planned Lunar missions will involve multiple NASA centers where each participating center has a specific role and specialization. In this vision, the Constellation program (CxP)'s Distributed System Integration Laboratories (DSIL) architecture consist of multiple System Integration Labs (SILs), with simulators, emulators, testlabs and control centers interacting with each other over a broadband network to perform test and verification for mission scenarios. To support the end-to-end simulation and emulation effort of NASA' exploration initiatives, different NASA centers are interconnected to participate in distributed simulations. Currently, DSIL has interconnections among the following NASA centers: Johnson Space Center (JSC), Kennedy Space Center (KSC), Marshall Space Flight Center (MSFC) and Jet Propulsion Laboratory (JPL). Through interconnections and interactions among different NASA centers, critical resources and data can be shared, while independent simulations can be performed simultaneously at different NASA locations, to effectively utilize the simulation and emulation capabilities at each center. Furthermore, the development of DSIL can maximally leverage the existing project simulation and testing plans. In this work, we describe the specific role and development activities at JPL for Space Communications and Navigation Network (SCaN) simulator using the Multi-mission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE) tool to simulate communications effects among mission assets. Using MACHETE, different space network configurations among spacecrafts and ground systems of various parameter sets can be simulated. Data that is necessary for tracking, navigation, and guidance of spacecrafts such as Crew Exploration Vehicle (CEV), Crew Launch Vehicle (CLV), and Lunar Relay Satellite (LRS) and orbit calculation data are disseminated to different NASA centers and updated periodically using the High Level Architecture (HLA). In addition, the performance of DSIL under different traffic loads with different mix of data and priorities are evaluated.

This article presents an initial set of results from the F-Interop European research project researching online platform for interoperability and performance tests for the Internet of Things. IoT interoperability testing is an important step for IoT solutions but current face-to-face testing is cost-inefficient and labor-intensive. F-Interop aims to provide online interoperability, conformance, and performance testing tools enabling remote tests. This article presents the challenges faced by the IoT in online testing, and how F-Interop is addressing them, in order to provide an extensive experimental platform for online tests. It gives an overview of its overall architecture and the developing online testing tools by F-Interop.

As part of the Department of Energy's (DOE) Gasification Technologies and Transportation Fuels and Chemicals programs, DOE and Texaco are partners through Cooperative Agreement DE-FC26-99FT40658 to determine the feasibility of developing, constructing and operating an Early Entrance Coproduction Plant (EECP). The overall objective of the project is the three-phase development of an EECP that produces at least one product from at least two of the following three categories: Electric power (or heat); Fuels; and Chemicals. The objective is to have these products produced by technologies capable of using synthesis gas derived from coal and/or some other carbonaceous feedstock, such as petroleum coke. The objective of Phase I was to determine the feasibility and define the concept for the EECP located at a specific site and to develop a Research, Development, and Testing (RD and T) Plan for implementation in Phase II. This objective has now been accomplished. A specific site, Motiva Refinery in Port Arthur, Texas, has been selected as the location best suited for the EECP. The specific work requirements of Phase I included: Prepare an EECP Preliminary Concept Report covering Tasks 2-8 specified in the Cooperative Agreement; Develop a Research, Development, and Testing (RD and T) Plan as specified in Task 9 of the Cooperative Agreement for implementation in Phase II; and Develop a Preliminary Project Financing Plan for the EECP Project as specified in Task 10 of the Cooperative Agreement. This document is the Preliminary Project Financing Plan for the design, construction, and operation of the EECP at the Motiva Port Arthur Refinery.

Avoiding concurrency errors remains one of the main challenges in day-to-day Erlang development. Errors can arise both from unexpected process and message interleaving, as well as concurrent clients or users interacting with the system in an unanticipated manner. To address this issue, many testing tools have been developed over the years. One approach is to pair a property-based testing tool with a tool that overrides the Erlang scheduler. This allows developers to focus on defining the properties of their system, and let the testing tools worry about testing these properties across different interleavings.This paper builds upon this approach and presents the Hansei testing framework. Hansei provides an approach to writing property-based tests that build on standard OTP abstractions, as well as a testing infrastructure designed to support test-driven development of concurrent systems. The Hansei infrastructure builds on the existing QuickCheck property-based testing tool, and supports both built-in message interleaving as well as a testing mode that works with existing process interleaving tools. Existing tools are more mature and feature-complete, while the built-in Hansei support has the unique property of being able to operate on code that spans multiple Erlang VMs.

A framework for performance and data quality assessment of Radio Frequency IDentification (RFID) systems in health care settings

: Three designs for a wing carrythrough structure developed in Phase Ia were further defined. Trade studies and design optimization studies were conducted to minimize cost and weight while meeting all design requirements including fracture mechanics requirements. Planning was completed on an extensive Development Test Program which included: Material Test Plan, Component Test Plan, Manufacturing Development Plan, and NDI Development Plan. All material was ordered for this development test program and material testing was underway on 6Al-4V beta processed material at the end of the reporting period. Manufacturing and NDI development had been started with the manufacturing and inspection of two 3 ft. x 4 ft. bonded ten-ply laminated panels using .125 6Al-4V annealed titanium and 33 brazed test specimens used to optimize the brazing process using Dynabraze B braze alloys and 6Al-4V beta processed titanium. Design studies were completed on the full-scale test fixture required for static, fatigue, and damage tolerance testing of the wing carrythrough structure. The 'V' fixed wing test fixture concept allowing application of loads to the WCTS without movement of the wing was selected for detail design and manufacture. (Author)