Showing papers on "Acceptance testing published in 2007"

Software Testing and Quality Assurance

Abstract: SOFTWARE QA AND TESTING RESOURCE CENTER. WELCOME PQA TESTING PROFESSIONAL QUALITY ASSURANCE LTD. FUZZING FOR SOFTWARE SECURITY TESTING AND QUALITY ASSURANCE. SOFTWARE QUALITY SOFTWARE TESTING FUNDAMENTALS. QUALITY ASSURANCE VS QUALITY CONTROL SOFTWARE TESTING. SOFTWARE TESTING WIKIPEDIA. SPECIALIST QA AMP SOFTWARE TESTING COMPANY TESTINGXPERTS. QUALITY ASSURANCE COMPANY QAWERK OUTSOURCE QA TO OUR. SOFTWARE QUALITY TESTING AND SECURITY ANALYSIS MCCABE. 15 1199 01 SOFTWARE QUALITY ASSURANCE ENGINEERS AND TESTERS. SOFTWARE QUALITY ASSURANCE PLAN SQAP TEMPLATE. SOFTWARE QA TRAINING QA COURSES ONLINE. BEST QUALITY ASSURANCE QA SOFTWARE TESTING TRAINING. IBETA QUALITY ASSURANCE. SOFTWARE TESTING CURRENT AFFAIRS 2018 APACHE COMMONS. SOFTWARE TESTING SERVICES SOFTWARE QUALITY ASSURANCE TESTING. SOFTWARE QUALITY ASSURANCE FROM THEORY TO IMPLEMENTATION. SOFTWARE QUALITY ASSURANCE SOFTWARE TESTING FUNDAMENTALS. SOFTWARETESTING AND QUALITY ASSURANCE TEST PLAN SAMPLE. SOFTWARE QA AND TESTING RESOURCE CENTER FAQ PART 1. PROGRAMMING FOUNDATIONS SOFTWARE QUALITY ASSURANCE. WHAT IS QUALITY ASSURANCE QA DEFINITION FROM WHATIS COM. ACUTEST IS THE LEADING INDEPENDENT SOFTWARE TESTING. QA SOFTWARE TESTING TRAINING QUALITY ASSURANCE ENGINEER. SOFTWARE QUALITY ASSURANCE. A1QA SOFTWARE TESTING COMPANY SOFTWARE QUALITY. QUALITY ASSURANCE WIKIPEDIA

Reconciling Manual and Automated Testing: The AutoTest Experience

Abstract: Software can be tested either manually or automatically. The two approaches are complementary: automated testing can perform a large number of tests in little time, whereas manual testing uses the knowledge of the testing engineer to target testing to the parts of the system that are assumed to be more error-prone. Despite this complementarity, tools for manual and automatic testing are usually different, leading to decreased productivity and reliability of the testing process. AutoTest is a testing tool that provides a "best of both worlds" strategy: it integrates developers' test cases into an automated process of systematic contract-driven testing. This allows it to combine the benefits of both approaches while keeping a simple interface, and to treat the two types of tests in a unified fashion: evaluation of results is the same, coverage measures are added up, and both types of tests can be saved in the same format

Enhancing the Efficiency of Regression Testing through Intelligent Agents

Abstract: Software testing is indispensable for all software development. As all mature engineering disciplines need to have systematic testing methodologies, software testing is a very important subject of software engineering. In software development practice, testing accounts for as much as 50% of total development efforts. Testing can be manual, automated, or a combination of both.Manual testing is the process of executing the application and manually interacting with the application, specifying inputs and observing outputs. Manually testing the software is inefficient and costly. It is imperative to reduce the cost and improve the effectiveness of software testing by automating the testing process, which contains many testing related activities using various techniques and methods. In order to automate the process, we have to have some ways to generate oracles from the specification, and generate test cases to test the target software against the oracles to decide their correctness. Today we still don't have a full-scale system that has achieved this goal. In general, significant amount of human intervention is still needed in testing. The degree of automation remains at the automated test script level. This paper therefore provides a timely summary and enhancement of agent theory in software testing ,which motivates recent efforts in adapting concepts and methodologies for agent oriented software testing to complex system which has not previously done. Agent technologies facilitate the automated software testing by virtue of their high level decomposition, independency and parallel activation[4]. Usage of agent based regression testing reduces the complexity involved in prioritizing the testcases.With the ability of agents to act autonomously, monitoring code changes and generating test cases for the changed version of the code can be done dynamically. Agent-Oriented Software testing (AOST) is a nascent but active field of research . A comprehensive methodology that plays an essential role in Software testing must be robust but easy-to use. Moreover, it should provide a roadmap to guide engineers in creating Agent-based systems. The agent based regression testing(ABRT) proposed here is to offer a definition for encompassing to cover the regression testing phenomena based on agents, yet sufficiently tight that it can rule out complex systems that are clearly not agent based.

Empirical analyses of executable acceptance test driven development

Abstract: This research investigates the process of Executable Acceptance Test-Driven Development (EATDD) in the context of specifying functional requirements using the FIT framework, when developing line-of-business applications. It is guided by three key research questions: (1) how business and technology experts utilize EATDD in the software development lifecycle; (2) what kind of benefits and limitations EATDD manifests, and (3) to what extent improvements in software quality (if any) are associated with EATDD? The research employs methods of quantitative and qualitative inquiries. Based on the findings of two academic observational studies, one academic quasiexperiment, and three industrial multi-case studies, the following main conclusions are drawn: (1) the use of Executable Acceptance Test-Driven Development is correlated with the enhanced communication in software teams; (2) executable acceptance tests are suitable for specifying functional requirements and are in fact unambiguous, consistent, verifiable, and usable (from both the business experts' and technology experts' perspectives); (3) EATDD provides sufficient evidence of requirements traceability in regulated environments; and (4) current state of tool support negatively impacts the maintainability and scalability of the artifacts produced in the course of EATDD. In addition, our contribution includes emerged conceptualizations and the sociotechnical model of the EATDD process. These not only help to explain the ways how EATDD is used in practice, but also form a base for future investigations.

Quality and timeliness in highway construction contracts: a new acceptance model based on both mechanical and surface performance of flexible pavements

Abstract: Timely completion and high performance are becoming key factors in modern road projects, so research is needed to have reliable contracts and acceptance criteria. The goal of this paper is confined to the formalization and validation of a unique model for the determination of pay adjustment on the basis of both quality (mechanical and surface performance of road pavements) and timeliness. Three main topics are addressed. The first is the estimation of pay adjustment (PA, negative or positive) when both structural and non‐structural deficiencies/surplus in characteristics are detected (e.g. low drainability in porous asphalt concretes). The second is the estimation of PA based on the quality of all the layers of the pavement. The third is the estimation of PA for early or late completion of the work. The formalized model is applied to an experimental case history. Analyses and validation demonstrate that the proposed model can efficiently solve typical problems in contract administration, in which decision...

Reliability and reproducibility of vertical diffusion cells for determining release rates from semisolid dosage forms.

Abstract: Purpose USP has formed Advisory Panels to ensure the integrity of laboratory procedures for non-oral routes of administration and expects that the panels will recommend performance tests (performance qualification, PQ) for these dosage forms as well as performance verification tests (PVT) for those PQ tests. An integral part of PQ is PVT, in which a standard formulation is first tested in a metrologically sound collaborative study to set acceptance criteria. Individual laboratories can then test the performance of their product by comparing their results to those obtained from the USP collaborative study. These studies are guided by metrological principles, e.g., those of the International Organization for Standardization (ISO) 43-1, which succinctly states that “one of the main uses of proficiency testing schemes is to assess laboratories’ ability to perform tests competently.”

An Assessment Of Astm F 2129 Electrochemical Testing Of Small Medical Implants - Lessons Learned

Abstract: Much has been learned over a short period of time with respect to the corrosion assessment of small medical implant devices Laboratory testing started with modifications of ASTM G 5 and G 61, which lead to the development of ASTM F 2129, and thence the fine-tuning of that specification to meet the intent of the FDA Guideline for non-clinical tests The changes in electrochemical testing protocol with time are reviewed Comparative data is presented addressing test environments, scan rates, statistical replication, alloy response, and acceptance criteria

Using traceability to support model-based regression testing

Abstract: Model-driven development is leading to increased use of models in conjunction with source code in software testing. Model-based testing, however, introduces new challenges for testing activities, which include creation and maintenance of traceability information among test-related artifacts. Traceability is required to support activities such as selective regression testing. In fact, most model-based testing automated approaches often concentrate on the test generation and execution activities, while support to other activities is limited (e.g. model-based selective regression testing, coverage analysis and behavioral result evaluation) To address this problem, we propose a solution that uses model transformation to create a traceable infrastructure of test-related artifacts. We use this infrastructure to support model-based selective regression testing.

Testing Non-Functional Requirements with Aspects: An Industrial Case Study

Abstract: Testing is regarded as one of the most resource consuming tasks of an average software project. A common goal of testing related activities is to make sure that requirements are satisfied by the implementation. Although existing tools are often effective in functional testing, emerging nonfunctional requirements set new demands. Aspect-oriented techniques offer a promising approach for capturing such issues under verification. However, prior to industrial adoption more pragmatic guidelines on applying aspects are required. In this paper, we evaluate aspect-oriented techniques in testing non-functional requirements of an industrial system. In addition, we discuss the types of requirements that lend themselves for more efficient testing using aspects than conventional techniques.

Software Testing Based on Formal Specification

Abstract: It is well accepted that formal specifications can be useful bases for software testing; some pioneering papers come back to the seventies Given a specification and a system under test, any testing activity is, explicitly or not, based on a satisfaction relation (often called conformance relation): does the system under test satisfy the specification? Tests are derived from the specification on the basis of the satisfaction relation, and often on the basis of some additional knowledge of the system under test and of its operational environment called testability hypothesis The verdict about the success or not of a test execution depends on the observations that can be made on the system under test, and it is based on the satisfaction relation

Using Statistical Analysis for Setting Process Validation Acceptance Criteria for Biotech Products

Abstract: This paper discusses the challenges of setting process validation acceptance criteria for biotech products for cases where using statistical tools is appropriate. Data are analyzed under three different scenarios that are frequently encountered in biotech applications. Scenario A represents the case when a small data set around center point conditions is available for setting acceptance criteria. Scenario B represents the case when a larger data set within normal operation conditions is available for setting acceptance criteria. Scenario C represents the case when a large characterization data set is available for setting acceptance criteria and it is possible to accurately model the impact of operation conditions on performance of the step. Statistical approaches including mean +/- 3SD, tolerance interval analysis, prediction profiler, and Monte Carlo simulation are applied to the different scenarios. Strengths and shortcomings of the different statistical tools are discussed, and the best approach for each scenario is recommended. It is shown that selection of the right statistical approach is a critical first step toward setting appropriate acceptance criteria.

Random testing: from the classical approach to a global view and full test automation

Abstract: Research has brought a number of different methods for automated test and test data generation in the last decades. These methods range from simple applications such as random testing, to complex analysis systems, such as constraint-based methods.While research on these methods has been extensive, industrial application to large-scale systems is still seldom. One of the reasons may be that the simple methods fail - e.g. in terms of achieved coverage -- for complex systems-under-test, while the complex methods are difficult to implement and often have limitations in terms of the language scope they can be applied to.This paper aims to present practical experience with a number of different methods based on random testing in various fields of application, ranging from automated unit tests to automated system and integration tests. This experience led to strategic combination of different methods, which shall be described and discussed based on actual results.

Evaluating Air-Entraining Admixtures for Highway Concrete

Abstract: This report presents a recommended procedure for evaluating air-entraining admixtures used in highway concrete. The procedure involves the testing of non-air-entrained concrete and concrete containing the air-entraining admixture under simulated field conditions. Criteria are proposed for acceptance of admixtures for use in either highway pavements or structures. The recommended procedure and acceptance criteria will guide materials engineers in evaluating and selecting air-entraining admixtures that should contribute to appropriate freeze-thaw durability and thus to good performance and long service life. The content of the report will be of immediate interest to materials engineers, researchers, and others concerned with the design of concrete mixtures for use in highway pavements and structures.

Talking tests: an empirical assessment of the role of fit acceptance tests in clarifying requirements

Abstract: The starting point for software evolution is usually a change request, expressing the new or updated requirements on the delivered system. The requirements specified in a change request document are often incomplete and inconsistent with the initial requirement document, as well as the implementation. Programmers working on the evolution of the software are often in trouble interpreting an under-specified change request document, resulting in code that does not meet the users' expectations and contains faults that can only be detected later through expensive testing activities.In this paper, we investigate the role of acceptance tests to clarify the requirements used in software evolution iterations. In particular we focus on Fit tables, a way to express acceptance tests which simplifies their translation into executable test cases. We designed and ran an experiment to assess whether availability of Fit tables affects the level of understanding and the productivity in understanding the requirements. Results indicate that Fit tables significantly improve requirement understanding, but tend to involve additional effort.

FitClipse: a fit-based eclipse plug-in for executable acceptance test driven development

Abstract: We conducted a survey on Executable Acceptance Test Driven Development (or: Story Test Driven Development). The results show that there is often a substantial delay between defining an acceptance test and its first successful pass. Therefore, it becomes important for teams to easily be able to distinguish between tasks that were never tackled before and tasks that were already completed but whose tests are now failing again. We then describe our FitClipse tool that extends Fit by maintaining a history of acceptance test results. Based on the history, FitClipse is able to generate reports that show when an acceptance test is suddenly failing again.

A Survey on Aspect-Oriented Testing Approaches

Abstract: Research on testing approaches for different programming paradigms has been done for several years. However, aspect-oriented programming (AOP), a relatively new programming paradigm, has properties that other programming paradigms do not have. These characteristics bring new challenges and issues not present when testing other types of programs such as object oriented programs (OOPs). So this new paradigm can not provide correctness by itself, and thus it also, like any other programs, requires the use of systematic testing approaches to produce validated and high quality software. This paper surveys the research on testing AOPs, the testing approaches that are being proposed, and issues that arise when testing AOPs. The effectiveness of proposed approaches is compared in terms of their ability to find different kind of faults as described by [6]. By making comparison on AOPs testing approaches, a better understanding of these approaches and issues related in testing AOPs is provided, as well as conclusion about existing state of research in this area and future trends for testing of aspect-oriented is identified.

Calibration of Nonnuclear Density Gauge Data for Accurate In-Place Density Prediction

Abstract: Hot-mix asphalt (HMA) density is an important acceptance quality characteristic, which involves in situ tests for quality control and assurance (QC/QA). Highway agencies have conventionally used nuclear density gauges or core samples for mat density. More recently, alternate nondestructive testing methods have been considered to replace current test methods. Nonnuclear density gauges offer rapid testing while eliminating safety risks and costs associated with radioactive license. Although agencies have evaluated them, they are not implemented in acceptance testing so far. Results are presented from a field evaluation of three nonnuclear density gauges—PaveTracker, PQI 300, and PQI 301—conducted on Wisconsin Department of Transportation (WisDOT) paving projects. The main goal was to evaluate the performance and effectiveness of nonnuclear gauges for use in QC/QA activities by WisDOT. The study involved field tests at 16 project sites and included 21 mix designs and a variety of mix design and pavement desi...

Validation of electrical power system using Electrical Test Bed of GEO satellite

Abstract: The electrical test bed (ETB) integrates the test environment, which is required for acceptance tests of system level, prior to FM testing. This ETB is composed of engineering version units of spacecraft BUS, which are laid on the laboratory table. It uses for the validation of system level functions and interface between each subsystem. The ETB also supports early functional and limited performance checkout of electrical subsystems and provides the environment for the verification of the Flight Software including AOCS, EPS, and TC&R simulators.

Requirements for information systems model-based testing

Abstract: In order to develop systems with a high level of quality and low costs it is necessary to have adequate testing tools and methods. We believe that the definition of a requirements catalog is one of the steps in such direction. This work presents a requirements catalog for information systems model-based testing that can be used as a basis for improving methods as well as a guide for the development of new methods and tools. The catalog was prepared based on the literature of the area and on the experience of several information systems developers.

Outlining Developers' Testing Process Model

Abstract: Most of the effort has been spent on formalizing processes for system testing. Little has been done regarding developers' unit and unit integration testing. In this paper, we study the routines of six developers when testing their software components. Our contribution is twofold. It first outlines a process model for unit and unit integration testing. It then provides feedback on the state of practice within six organizations.

Method of acceptance for semiconductor devices

Abstract: A method of accepting semiconductor chips is provided using on-chip parametric measurements. An on-chip parametric measurement structure is determined for each parameter in a set of parametric acceptance criteria. An on-chip parametric measurement macro is included in a design of each semiconductor chip for each identified on-chip parametric measurement structure. Each on-chip parametric measurement macro is tested to determine compliance of the semiconductor chip to the set of parametric acceptance criteria. Compliance to the set of parametric acceptance criteria is validated.

Reliability analysis of project and product type software in operational phase incorporating the effect of fault removal efficiency

Abstract: Since the early 1970's numerous Software Reliability Growth Models (SRGM) have been proposed in the literature to estimate the software reliability measures such as the remaining number of faults, failure rate and reliability growth during the testing phase. These models are applied to the software testing data collected during the testing phase and then are often used to predict the software failures in operational phase. In practice simulating mirror image of the diverse testing environment representative of the operational environment is difficult in practice and hence the simulated testing environment during the testing phase may not be similar to the conditions that exist in the operational phase. During testing phase testing is performed under a controlled environment whereas during the operational phase failure phenomenon depends on the operational environment and usage of software. Therefore an SRGM developed for the testing phase is not suitable for estimating the reliability growth during the operational phase. In this paper, we propose a generalized Software Reliability Growth Model, which can be used to estimate number of faults during the testing phase and can be easily extended to the operation phase. In the testing phase, it is appropriate to estimate the reliability growth with respect to the amount of testing resources spent on testing whereas in the operational phase the amount of effort to be spent on removing a fault reported by a user is fixed by the developer. The number of failures detected and hence the reliability growth during the user phase depends on the usage of software. The proposed model appropriately incorporates these changes. Further we categorize the software into two-categories- (a) project and (b) product type software. Appropriate usage functions are linked to both project and product type software. To describe the fault removal phenomenon, imperfect debugging environment is incorporated into the model building. The paper highlights an interdisciplinary mathematical modeling approach in Software Reliability Engineering and Marketing. The proposed model is validated for both phases using the software failure data sets obtained from different sources. Model describes the failure phenomenon for these data sets fairly.

CBS testing requirements and test case process documentation revisited

Abstract: Component-based software testing is an important capability that supports productivity and quality assurance in component-based software development. The increased size and complexity of software systems has led to the current focus on developing distributed applications that are constructed primarily using components. Thus, the component-based systems require efficient and effective ways to test these systems and need to develop effective techniques for testing various aspects of the components such as reusability, security, dependability and safety. Study on the subject by several researchers indicates that more than fifty percent of the cost of software development is devoted to testing and it results into very high cost for testing complex software. The present paper is aimed at improving component-based system testing while considering two factors: component-based system testing requirement and test case process documentation. Lastly, the paper also discusses the limitations of component-based software testing that hinders component-based development.

"Talking tests": a Preliminary Experimental Study on Fit User Acceptance Tests

Abstract: This short paper reports a pilot experiment conducted with master students, in which we investigated whether fit test cases were helpful to clarify change requirements in a maintenance task.

Comparisons of Contractor and State Transportation Agency Quality Assurance Test Results on Mat Density of Hot-Mix Asphalt Concrete: Findings of Multistate Analysis

Abstract: A typical component of highway construction quality assurance programs is the process by which highway construction elements are sampled and tested to ensure compliance with specifications and other project requirements. The results of contractor-performed tests on in-place properties of hot-mix asphalt are increasingly used in the acceptance decision in many states. Results of tests performed by contractors and state departments of transportation (DOTs) in North Carolina, Florida, and Kansas consistently indicate that differences between contractors and state DOT test results for hot-mix asphalt concrete mat density are statistically significant. Furthermore, these comparisons consistently indicate less variable and more favorable contractor test results, relative to specification limits, that give more favorable acceptance outcomes. Details of quality assurance processes (sampling and testing frequencies, test methods, verification procedures, and acceptance procedures) appear to have little if any effe...

Interoperability testing for shop floor measurement

Abstract: Manufactured parts are typically measured to ensure quality. Measurement involves equipment and software from many different vendors, and interoperability is a major problem faced by manufacturers. The I++ Dimensional Measuring Equipment (DME) specification was developed to solve interoperability problems and enable seamless flow of information to and from dimensional metrology equipment. This paper describes validation testing of the I++ DME specification. The testing was intended to improve the specification and also to speed up its adoption by vendors. Testing issues are described, and a software test suite is detailed. Interoperability testing with real equipment was done over several years, and lessons learned from the testing will be presented. The paper concludes with recommendations for improving this type of testing.

An extensible framework for distributed testing of MPI implementations

Abstract: Complex code bases require continual testing to ensure that both new development and routine maintenance do not create unintended side effects. Automation of regression testing is a common mechanism to ensure consistency, accuracy, and repeatability of results. The MPI Testing Tool (MTT) is a flexible framework specifically designed for testing MPI implementations across multiple organizations and environments. The MTT offers a unique combination of features not available in any individual testing framework, including a built-in multiplicative effect for creating and running tests, historical correctness and performance analysis, and support for multiple cluster resource managers.