Measuring software testing efficiency using two-way assessment technique

Software testing process is an important factor affecting the quality of software testing, which plays an important role in the entire software development life cycle. In order to achieve a precise result of testing, different software testing process model will be chosen in different software development process for testing. Traditional testing process model will be chosen in traditional software development, and agile testing process model will be chosen in agile software development. However, there is no kind of testing process model proposed for a special software development which is a combination of traditional software development and agile software development. This article will propose a hybrid software testing process model aiming at a combination of traditional software development model and agile software development model. In the following sections, traditional testing process model and agile testing process model will be introduced respectively in the first place. Most attentions will be paid to the introduction and analysis of the hybrid software testing process model through one case. Furthermore, we will discuss the relationship of the data tracing involved in the testing process model.

Today, the most vital step is software testing, especially in product quality. Agile software development is exceedingly difficult and has contentious issues in literature and business. Since most Agile techniques place more emphasis on development than software testing activities, different people have varying opinions about how software testing fits into these methodologies. Agile places a high emphasis on frequent deliveries and tight client connections. However, software testing is complex because agile does not incorporate many destructive testing techniques typically required for a product of higher-quality. The study reveals industry-wide Agile testing procedures and the main problems that arise when Agile development is used. Additionally covered are the differences between manual and automated testing, best automation practices, and ways to lead different testing teams in an agile testing environment. This study covers every facet of the Agile software testing process. Agile development has shown that testing is not a distinct stage but rather a crucial component of software development along with the coding. The agile team employs an overall strategy to produce software products of the highest quality. As part of an agile team, testers collect customer samples of the desired behaviour and collaborate with the developer's team to help the coders translate these examples into executable specifications. Coding and testing are done iteratively and incrementally, developing every item until it is valuable enough to release in production. It addresses several testing modalities. The classification provided by its quadrants aids teams in determining and organizing the necessary tests. To increase quality assurance, this article will examine various and improved Agile Testing Processes and methodologies. Additionally, the topic of Agile development's software testing method is covered. Agile development processes can be improved and more advantageous by incorporating testing procedures.

Putting Requirements and Quality at the Core of Global Service Delivery: Current Efforts and Future Plans at Pace University

Background: The development of technology, both hardware and software, is rapidly advancing due to the growth of Artificial Intelligence (AI), which simplifies many human activities, including the software testing process. This research journal discusses how software testing is conducted through a Quality Management System (QMS). Objective: The journal examines whether software testing processes are related to QMS, how significantly QMS supports software testing, and the differences between testing with QMS and without QMS. Methods: This study outlines the stages of software testing through QMS, such as Software Quality Assurance (SQA), Quality Control (QC), Test Maturity Model Integration (TMMI), and performance indicators. According to the American Society for Quality (ASQ), QMS is a formal and documented system consisting of policies, processes, and procedures designed to achieve an organization's quality policies and objectives. Results: Several experts also define QMS as a system that focuses on improving customer satisfaction, process consistency, efficiency, and the overall quality of products or services. Software, according to Roger S. Pressman, is a set of instructions (programs), data structures that allow information manipulation, and related documentation describing operations and functions. Conclusion: Overall, QMS not only improves software product quality but also strengthens the testing process, making it more optimal, efficient, and aligned with organizational goals. The integration of QMS frameworks such as ISO 9001:2015, CMMI, and TMMI provides organizations with a competitive advantage by ensuring consistent delivery of high-quality software products that meet or exceed customer expectations.

Software testing is an important process in software quality assurance(SQA). Software testing consumes the majority of the software developers' time and cost of all the phases of system development. An important problem in software testing is to determine whether a program has been tested enough with a testing criterion and when one could stop testing. On the other hand, software measurement is used to estimate the quality of a software. Complexity measures can be used to compare software quality and development cost. This paper proposes a new testing approach which choosing testing path based on path complexity. The process is to use a set of testing paths that satisfying all-uses testing criterion, and then choose the testing path with the most complexity to test. This process is continued until the program can be accepted. The proposed formula is used to determine if it is possible to stop testing before satisfying all-du-paths testing criterion. The main contribution of the paper is that software developers can choose a proper testing action with lower testing effort.

Software testing is an extremely important work link in software engineering. It runs through the entire life cycle of software engineering to ensure that software development meets requirements and can meet certain software quality requirements. With the continuous expansion of the scale of information systems, simple software testing can no longer meet the requirements of system and software quality assurance. This requires practitioners to gradually begin to think about and improve the testing methods of large-scale information software. For large-scale information software, testing will be embedded in each unit, and the software testing process will be organized in a more macroscopic way of thinking and organization. This article will summarize a series of methods suitable for large-scale information software testing through the research of software testing and the practice of the author. It is hoped that the research in this article can provide some help for the testing of large-scale information software, and also provide help for the precipitation and improvement of the author's own work.

In the context of the rapid development of information technologies, software quality is becoming critical for the successful operation of organizations in various industries. The growing complexity of modern software solutions requires the involvement of highly qualified specialists in software testing and quality assessment, capable of effectively identifying shortcomings and ensuring that the product meets established standards. At the same time, assessing the level of competence of such experts remains a difficult task, which is often based on subjective criteria and methods. The relevance of the study is due to the acute need of the modern IT market for objective tools for assessing the professional level of specialists, especially in the field of software quality assurance. Traditional approaches to qualification assessment, such as interviews, test tasks or resume analysis, often do not provide a complete and objective picture of the expert's competence. This problem becomes especially acute in the conditions of the global labor market, when companies are forced to evaluate specialists remotely, relying only on a limited set of data on their experience and skills. Today, software has become an integral part of many areas of our everyday life - from automation and optimization of production processes to creating comfort for an individual. The object of the study is the process of determining the level of competence of experts in software quality assessment. The subject of the study is a mathematical model for calculating the level of competence of an expert. The practical value of the results of the work is determined by the possibility of using the developed system by HR managers for effective selection of specialists, by heads of QA departments for the formation of balanced testing teams, by certification centers for objective assessment of competence, as well as by the experts themselves for planning their own professional development. Conclusion the developed mathematical model for calculating the level of competence of an expert allows you to reduce the time for assessing the competence of specialists, minimize the influence of subjective factors when making personnel decisions, and optimize the distribution of human resources in software development and testing projects.

: With regard to software testing in DoD, we can summarize our conclusions in two fundamental ideas. First, DoD knows how to produce quality software at low cost. This is because organizations such as DoD STEP, Army STEP, and Software Engineering Institute have already researched and documented policies for DoD. A few commercial software developers practice many of the DoD policies and directives now, and produce quality software (for example, IBM FSC Houston). Second, quality cannot be tested into software. Only a well-defined, well-disciplined process with a continuous improvement cycle can ensure software quality. However, testing cannot be underestimated. Systematic testing activities that detect error earliest in the life cycle are necessary to drive process improvement and optimize the development of quality software. Such testing methods as formal inspection find defects early. This enables cost- effective error resolution, identification and removal of defect causes, and thus, prevention of future defect insertion. If practiced with discipline, such methods can evolve a self-correcting software development process that is stable, modeled, measured, and therefore, predictable. This development process engineers quality software faster at reduced cost.... Software testing, Software quality, Formal inspection, Quality control.

We empirically examine the relationship between software design modularity and software quality in open source software (OSS) development projects. Conventional wisdom suggests that degree of software modularity affects software quality. An analysis of 203 software releases in 46 OSS projects hosted on SourceForge.net lends support for a more complex relationship between software modularity and software quality than conventional wisdom suggests. We find that software modularity is associated with reduced software complexity, an increased number of static software bugs, and a mixed relationship with the percentage of bugs closed. We do not find empirical evidence supporting any relationship between modularity and other measures of customer satisfaction. In addition to empirically testing the relationship between modularity and quality, we introduce new measures of software modularity and software quality. Implications are developed for the theory of modularity and the practice of software development.

In the software industry, software testing becomes more important in the entire software development life cycle. Software testing is one of the fundamental components of software quality assurances. Software Testing Life Cycle (STLC)is a process involved in testing the complete software, which includes Regression Testing, Unit Testing, Smoke Testing, Integration Testing, Interface Testing, System Testing & etc. In the STLC of Regression testing, test case selection is one of the most important concerns for effective testing as well as cost of the testing process. During the Regression testing, executing all the test cases from existing test suite is not possible because that takes more time to test the modified software. This paper proposes new Hybrid approach that consists of modified Greedy approach for handling the test case selection and Genetic Algorithm uses effective parameter like Initial Population, Fitness Value, Test Case Combination, Test Case Crossover and Test Case Mutation for optimizing the tied test suite. By doing this, effective test cases are selected and minimized the tied test suite to reduce the cost of the testing process. Finally the result of proposed approach compared with conventional greedy approach and proved that our approach is more effective than other existing approach.

Small software companies make for the majority of software companies around the world, but their software development processes are often not as clearly defined and structured as in their larger counterparts. Especially the test process is often the most neglected part of the software process. This contribution analyses the software testing process in a small South African IT company, here called X, to determine the problems that currently cause it to deliver software fraught with too many defects. The findings of a survey conducted with all software developers in company X are discussed, and several typical problems are identified. We also discuss two prevalent test process improvement models that can be used to reason about the possibilities of process improvement. Solutions to those (or similar) problems often already exist, but a major part of the problem addressed in this contribution is the unawareness, or unfamiliarity, of many small industrial software developers and IT managers as far as the scientific literature on software science and engineering, and especially in our case: software testing, is concerned.

Software reliability testing refers to various software testing activities that are driven to achieve a quantitative reliability goal given a priori or lead to a quantitative reliability assessment for the software under test. In this paper we develop a modeling framework for the software reliability testing process, comprising a simplifying model and a generalized model. In both models the software testing action selection process and the defect removal mechanism are explicitly described. Both the discrete-time domain and the continuous-time domain are involved. The generalized model is more accurate or realistic than the simplifying model since the former avoids the assumption that defects are equally detectable and the assumption that defects are removed upon being detected. However simulation examples show that the simplifying model really captures some of essential features of the software testing process after a short initial testing stage. The modeling framework is practically realistic, mathematically rigorous, and quantitatively precise. It demonstrates that the relationship between software testing and delivered software reliability, which was poor understood, can well be formulated and quantified. Rigorous examinations show that several common assumptions adopted in software reliability modeling, including the independence assumption, the exponentiality assumption, and the NHPP assumption, are theoretically false in general. This paper sets a good starting point to further formalize and quantify the software testing process and its relation to delivered software reliability.

In order to enhance the software quality, control and improve software testing process, the software testing process needs to be effectively measured. This paper presents a goal-driven measurement model for software testing process (MMSTP). Based on MMSTP, software organizations can deduce the appropriate measurement process according to the process goals they determine. At the same time, they also can get the direction of testing process, which will provide an effective support for make the correct decision to better the testing process.

Here are obstacles in the process of making software at PT. Hartono Technology Palace. At that time, every time a test was carried out on the software being developed, the company would find different results. This causes ineffective and inefficient software development processes. Problems at PT. Hartono Istana Teknologi was found because of the less use of standard software testing methods. That is why the test results are constantly changing, and the software development process cannot be completed quickly. This problem can be solved by applying the software testing method. This research will try to solve the problem by using 2 methods, trial and error, and integration. These two methods will be compared to determine which method is more effective in the software testing process at PT. Hartono Technology Palace. Several test scenarios are also designed to be applied in this study. As a final result, the trial and error method is the most effective method to be applied at PT. Hartono Istana Teknologi. The trial and error method is considered effective because the testing process is more thorough and in accordance with the established concept. While in the integration method, the testing process only focuses on testing data without paying attention to existing functions

Adaptive software testing is the counterpart of adaptive control in software testing. It means that software testing strategy should be adjusted online by using the testing data collected during software testing as our understanding of the software under test improves. Previous studies on adaptive testing rely on a simplified Controlled Markov Chain (CMC) model for software testing which employs several unrealistic assumptions. In this paper we propose a new adaptive software testing approach in the context of an improved CMC model which aims to eliminate such threats to validity. A new set of basic assumptions on the software testing process is proposed and several unrealistic assumptions are replaced by more common situations in real life software testing. The methodology of a new adaptive testing strategy is also developed and implemented. Experimental data are collected to demonstrate the effectiveness of the new methodology.