Component-based Software Testing Research Articles

Retracted: Component-Based Software Testing Method Based on Deep Adversarial Network

Retracted: Component-Based Software Testing Method Based on Deep Adversarial Network

Component-Based Software Testing Method Based on Deep Adversarial Network

With the continuous updating and application of software, the current problems in software are becoming more and more serious. Aiming at this phenomenon, the application and testing methods of componentized software based on deep adversarial networks are discussed. The experiments show that: (1) some of the software has a high fusion rate, reaching an astonishing 95% adaptability. The instability and greater potential of component-based software are solved through GAN and gray evaluation. With the evaluation system, people are dispelled. Trust degree. (2) According to the data in the graph and table, the deep learning adversarial network solves the vulnerability and closedness of the general network, and the built-in test method with experimental data reaching an average accuracy rate of 90% is the best test method for this system. With the deep learning adversarial network, the average test level of component-based software reaches level 7, which makes the new software industry of component-based software have a long way to go.

Direct-Indirect Link Matrix

Testing of software remains a fundamentally significant way to check that software behaves as required. Component-based software testing (CBST) is a crucial activity of component-based software development (CBSD) and is based on two crucial proportions: components testing by developers with the source code (e.g., system testing, integration testing, unit testing, etc.) and components testing by end users without source code (black box testing). This work proposes a black box testing technique that calculates the total number of interactions made by component-based software. This technique is helpful to identify the number of test cases for those components where availability of source code is questionable. On the basis of interaction among components, the authors draw a component-link graph and a direct-indirect-link matrix, which helps to calculate the number of interactions in component-based software.

A Novel Approach to Component-Based Software Testing

In the present era when component-based software development plays an important role in the software development community, testing is an important activity, which should not be neglected. Component-based software testing is an essential activity, which supports productivity in component-based software development. Past studies indicate that more than fifty percent of the cost of software development is dedicated to the testing activity, which results in an increased cost of the software. This paper describes the issues and challenges of component-based systems. This paper also suggests the requirement of a novel approach to testing of component-based software. It also proposes a novel approach to testing of component-based software while considering some important factors like component study, component test case design, component test execution, and component test analysis and component test documentation.

Research on Evaluation of Component-Based Software Testing

The research object of our work is evaluating program for the component-based software testing. As an important part into the software engineering, software testing is the primary instrumentality to guarantee the quality and reliability of the software. With the Component-Based Software Development (CBSD) method becoming a popular method of software engineering, people pay more and more attention to the quality of component software. Therefore, the component-based software testing is an important method to guarantee the quality of component software. There are many factors existing in the component-based software testing process, in order to avoid some errors and defects and improve the testing process, we need evaluate the validity of component-based software testing. Based on the discussion of the quality characteristics of the software component, the study studies the workflow and the relevant measures which apply to evaluate the validity of component-based software testing.

A Systematic State-Based Approach to Regression Testing of Component Software

Today, component-based software engineering has been widely used in software construction to reduce project cost and speed up software development cycle. Due to software changes in new release or update of components, regression testing is needed to assure system quality. When changes made to a component, the component could be affected, moreover, the changes could bring impacts on the entire system. We firstly identify diverse changes made to components and system based on models, then perform change impact analysis, and finally refresh regression test suite using a state-based testing practice. Related existing research did not address the issue of systematic regression testing of component-based software, especially at system level. The paper also reports a case study based on a realistic component-based software system using a, which shows that the approach is feasible and effective.

Testing component compatibility in evolving configurations

Software components are increasingly assembled from other components. Each component may further depend on others, and each may have multiple active versions. The total number of configurations—combinations of components and their versions—in use can be very large. Moreover, components are constantly being enhanced and new versions are being released. Component developers, therefore, spend considerable time and effort doing compatibility testing—determining whether their components can be built correctly for all deployed configurations–both for existing active component versions and new releases. In previous work we developed Rachet, a distributed, cache-aware mechanism to support large-scale compatibility testing of component-based software with a fixed set of component versions.In this paper, we observe that it is too expensive to perform compatibility testing from scratch each time a new version of a component is released. We thus add a new dimension to Rachet: to perform incremental and prioritized compatibility testing. We describe algorithms to compute differences in component compatibilities between current and previous component builds, a formal test adequacy criterion based on covering the differences, and cache-aware configuration sampling and testing methods that attempt to reuse effort from previous testing sessions. Because testers are often interested in focusing test effort on newly released and modified components and their versions, we have developed a prioritization mechanism that enhances compatibility testing by examining the configurations that test new or modified component versions first, while also distributing the work over a cluster of machines. We evaluate our approach using the 5-year evolution history of a scientific middleware component. Our results show that our methods can increase performance significantly over Rachet’s previous retest-all approach and also tests important component compatibilities early in the overall testing process, making the process of compatibility testing practical for evolving components.

Testing Component-Based Software: What It has to do with Design and Component Selection

In a component-based software development life cycle, selection of preexisting components is an important task. Every component that has to be reused has an associated risk of failure of not meeting the functional and non-functional requirements. A component's failure would lead a developer to look for some other alternative of combinations of COTS, in-house and engineered components among possible candidate combinations. This means design itself can readily change. The very process of design of a software system and component selection seems to be heavily dependent on testing results. Instability of design, further, becomes more severe due to requirements change requests. Therefore, this instability of design has to be essentially mitigated by using proper design and testing approaches, otherwise, it may lead to exorbitantly high testing cost due to the repeated testing of various alternatives. How these three activities: Component-based software design, component selection and component-based software testing are interrelated? What process model is most suited to address this concern? This work explores the above questions and their implication in terms of nature of a process model that can be convincing in case of component-based software development.

Reliability Analysis of Component Software in Wireless Sensor Networks Based on Transformation of Testing Data

We develop an approach of component software reliability analysis which includes the benefits of both time domain, and structure based approaches. This approach overcomes the deficiency of existing NHPP techniques that fall short of addressing repair, and internal system structures simultaneously. Our solution adopts a method of transformation of testing data to cover both methods, and is expected to improve reliability prediction. This paradigm allows component-based software testing process doesn’t meet the assumption of NHPP models, and accounts for software structures by the way of modeling the testing process. According to the testing model it builds the mapping relation from the testing profile to the operational profile which enables the transformation of the testing data to build the reliability dataset required by NHPP models. At last an example is evaluated to validate and show the effectiveness of this approach.

CBS testing requirements and test case process documentation revisited

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.