Software Testing (Computer Science)

Ina software testing domain, different techniques and
approaches  are  used  to  support  the  process  of
regression  testing  in  an  effective  way.  The  main
approaches  are  test  suite  minimization,  test  case
prioritization  and  test  case  selection.  Test  case
prioritization  techniques  improve  the  performance  of
regression  testing,  and  arrange  test  cases  in  order  to
obtain  maximum  available  fault  that  is  going  to  be
detected  in  a  shorter  time.  User-sessions  and  cookies
are unique features of web applications that are useful
in  regression  testing  because  they  have  precious
information about the application state before and after
any change that is made to the software code. The main
challenge  is  the  effectiveness  of  average  percentage
fault detection rate and time constraint in the existing
techniques. Thus, in this research the priority is given
to  clustering  test  cases  that  are  performed  based  on
some  criteria  related  to  http  requests  which  collected
from  the  database  of  server  side.  To  verify  the  new
technique  some  fault  will  be  seeded  in  subject
application  then  applying  the  prioritization  criteria  on
test  cases  for  comparing  the  effectiveness  of  average
percentage  fault  detection  rate  and  time  with  existing
techniques.

This article appeared in a journal published by Elsevier. The attached copy is furnished to the author for internal non-commercial research and education use, including for instruction at the authors institution and sharing with colleagues. Other uses, including reproduction and distribution, or selling or licensing copies, or posting to personal, institutional or third party websites are prohibited. In most cases authors are permitted to post their version of the article (e.g. in Word or Tex form) to their personal website or institutional repository. Authors requiring further information regarding Elsevier's archiving and manuscript policies are encouraged to visit: http://www.elsevier.com/copyright a b s t r a c t Software testing is an important but complex part of software development life cycle. The optimization of the software testing process is a major challenge, and the generation of the independent test paths remains unsatisfactory. In this paper, we present an approach based on metaheuristic firefly algorithm to generate optimal test paths. In order to optimize the test case paths, we use a modified firefly algorithm by defining appropriate objective function and introducing guidance matrix in traversing the graph. Our simulations and comparison show that the test paths generated are critical and optimal paths.

While a wide range of different, sometimes heterogeneous test coverage criteria have been proposed, there exists no generic formalism to describe them, and available test automation tools usually support only a small subset of them. We introduce a unified specification language, called HTOL, providing a powerful generic mechanism to define test objectives, which permits encoding numerous existing criteria and supporting them in a unified way. HTOL comes with a formal semantics and can express complex requirements over several executions (using a novel notion of hyperlabels), as well as alternative requirements or requirements over a whole program execution. A novel classification of a large class of existing criteria is proposed. Finally, a coverage measurement tool for HTOL objectives has been implemented. Initial experiments suggest that the proposed approach is both efficient and practical.

Debugging large-scale parallel applications is challenging. In most HPC applications, parallel tasks progress in a coordinated fashion, and thus a fault in one task can quickly propagate to other tasks, making it difficult to debug. Finding the least-progressed tasks can significantly reduce the effort to identify the task where the fault originated. However, existing approaches for detecting them suffer low accuracy and large overheads; either they use imprecise static analysis or are unable to infer progress dependence inside loops. We present a loop-aware progress-dependence analysis tool, Prodometer, which determines relative progress among parallel tasks via dynamic analysis. Our fault-injection experiments suggest that its accuracy and precision are over 90% for most cases and that it scales well up to 16,384 MPI tasks. Further, our case study shows that it significantly helped diagnosing a perplexing error in MPI, which only manifested at large scale.

Summary: The page describes some of the problems in QA Automation that occur when using UIAutomation (CodedUI, White) to automated desktop applications and methods for their solution on the example of the project developed with DevExpress library.

—We introduce covrel, an adaptive software testing approach based on the combined use of operational profile and coverage spectrum, with the ultimate goal of improving the delivered reliability of the program under test. Operational profile-based testing is a black-box technique that selects test cases having the largest impact on failure probability in operation; as such, it is considered well suited when reliability is a major concern. Program spectrum is a characterization of a program's behavior in terms of the code entities (e.g., branches, statements, functions) that are covered as the program executes. The driving idea of covrel is to complement operational profile information with white-box coverage measures based on count spectra, so as to dynamically select the most effective test cases for reliability improvement. In particular, we bias operational profile-based test selection towards those entities covered less frequently. We assess the approach by experiments with 18 versions from 4 subjects commonly used in software testing research, comparing results with traditional operational and coverage testing. Results show that exploiting operational and coverage data in a combined adaptive way actually pays in terms of reliability improvement, with covrel overcoming conventional operational testing in more than 80% of the cases.

The International Journal of Software Engineering & Applications (IJSEA) is a bi-monthly open access peer-reviewed journal that publishes articles which contribute new results in all areas of the Software Engineering & Applications. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on understanding Modern software engineering concepts & establishing new collaborations in these areas.

Software testing is the SDLC's important and most expensive step. Software testing is difficult and time-consuming work requiring a great deal of money for software development. Testing is both an operation that is static and adaptive. Software testing process deals with the creation of test cases, checking and validating either passed or failed test cases. It is unidealistic to check only the discerning parts of the material as a whole at once. It is not possible to test the whole system once, so selected parts of the code are considered for analysis. Since the input space of the Product Under Test (PUT) can be very large, it is important to analyze a representative subset of test cases. During software testing, the most important task is to build appropriate test cases. An effective set of test cases can detect more errors. Software testing always requires high deficiencies. Test cases are constructed using the test data. In the automation of software testing, the important task is to generate test data according to a given level of competence. The improved test data are determined using the test case development methodology and the test data adequacy criterion being applied. For increase the level of automation and performance, these aspects of test case development need to be studied. This paper studies the various test case generation techniques using soft computing techniques like Genetic Algorithm, Artificial Bee colony methods. Further an evaluation criterion for the test case generation process, empirical study of Code Coverage and its importance is discussed.

In 1996, June 4th the European Space Agency launched a rocket named Ariane 5 which exploded in just 40 seconds after its launch from Kourou, French Guiana. It took 10 year for the European Space Agency to build the rocket and its development cost was $7 billion. The rubble of the exploded rocket were found across the mangrove swamps of French Guiana. A board of inquiry investigated the reason behind the explosion was due to a software error in the inertial reference system. The conversion failed of a 64 bit floating point number to the horizontal velocity of the rocket with respect to the platform was converted to a 16 bit signed integer. The number was larger than 32,767, the largest integer that can fit in a 16 bit signed integer.

The Process of developing error free application known as code testing. The bug free code production is that the aims of testing team that carrier in each level of testing. To succeed in the standard of product, code testing may be a helpful method. Testing eliminates all defect by providing various options and useful to scale back the price of code. Testers aim to produce code with low maintenance value. However the main issue in checking is to seek out appropriate test cases to check the code. We've got many advances in testing. However still the code has got to be completely tested before it's delivered to the client. during this paper, numerous forms of testing, its objective outlined and conjointly describe the code checking life cycle and test cases and phases are describe very well with their importance and significance.

Introduction Now a days Internet of Things is very important topic all over the technological world and has become very much popular on Social media and Press media. The Phrase Internet of Things is a combination of two: One is the Internet (Network) and second is Things (Any object). The internet of things is the network of physical devices or objects/Things like: Vehicles, Home appliances, Industrial equipment, Office devices and Hospitals machines and also other things rooted with electronic devices, software, sensor devices, actuators and network connectivity-that enables these objects to communicate over a network. The internet of Things is a system of interconnected computing devices that refers with Human-to-Human, Things-to-Things and Human-to-Things over a shared network. The Internet of Things technology has a wide range of networked products, systems, devices, sensors and objects having advantages of advancements in computing power, electronic miniaturization, and network interconnections to offer new capabilities not previously possible. In others word, the Internet of Things (IoT) refers to the capability of every day devices to connect to other devices and also people through the existing Internet Infrastructures. That devices connect and communicate in many ways. A huge scale of business proposals, business-conferences and debates has discussed that IoT is revolution for new technologies, Like; new market research and business models to concerns more about security, privacy, comfort, reliability and technical interoperability. For Example: like Smart devices interaction with another smart devices, Smartphones that interact with other smartphones over a network, Vehicle-to-Vehicle communication, Smartphones connected with home appliances, Smart Devices connected with video cameras, and medical devices.

8th International Conference on Artificial Intelligence and Soft Computing (AIS 2022) will provide an excellent international forum for sharing knowledge and results in theory, methodology, and applications of Artificial Intelligence, Soft Computing. The Conference looks for significant contributions to all major fields of the Artificial Intelligence, Soft Computing in theoretical and practical aspects. The aim of the Conference is to provide a platform to the researchers and practitioners from both academia as well as industry to meet and share cutting-edge development in the field.

One of the most important tasks that business managers and owners face is the formation of an organizational structure as it determines the future of a company. This task is challenging to managers, but its benefits to the company are long-term. Organizational structure is best understood when illustrated in an organizational chart that details the flow of project tasks to be completed by team members.

In a variety of software development methods and their models of the activity process, no one does not have testing activities in their application. System testing is the last phase of testing that done by the developer in the internal work-space. However, phase of testing is not the end of the whole testing phase, since there is another stage to pass before the product deployment process, it is the acceptance testing. A popular method to perform the user acceptance testing is the usability testing, which in this method, the result provides the indication of the essential quality for the client to decide whether to approve or to deny the product. In this research of paper, we are going to do the usability testing by utilizing the System Usability Scale technique and the Net Promoter Score technique to measure appropriateness of the population information systems in the city of Tegal while we are also finding optimum testers required using the sampling technique. The result we earn trough this research is according to the Usability Testing result the proposed system developed by researchers is better than the current running system and the total testers participating on system testing is able to optimize using the sampling method.

Summary: The brochure describes some of the problems in QA Automation that occur when using UIAutomation (CodedUI, White) to automate desktop applications and methods for their solution on the example of the project developed with DevExpress library. There are also some useful examples of using PowerShell scripts in both daily tasks in CI (continuous integration) (TFS, Azure) - e.g. application deployment. Some architectural examples of developing test automation framework using application related files are also discussed. System programming could be a powerful weapon when need to solve some specific issues - LogonUser, update systime, get temp file and Processes, etc.

Software Engineering (SE) is a wide domain, where ontologies are useful instruments for dealing with Knowledge Management (KM) related problems. When SE ontologies are built and used in isolation, some problems remain, in particular those related to knowledge integration. The goal of this paper is to provide an integrated solution for better dealing with KM-related problems in SE by means of a Software Engineering Ontology Network (SEON). SEON is designed with mechanisms for easing the development and integration of SE domain ontologies. The current version of SEON includes core ontologies for software and software processes, as well as domain ontolo-gies for the main technical software engineering subdomains, namely requirements , design, coding and testing. We discuss the development of SEON and some of its envisioned applications related to KM.

One of the very important aspects of software quality is software testing. Software testing consumes 30%-50% of the most software projects. Testing should not only be performed for the quality or development process requirement but due to the fact that testing needs to ...

The International Journal of Software Engineering & Applications (IJSEA) is a bi-monthly open access peer-reviewed journal that publishes articles which contribute new results in all areas of the Software Engineering & Applications. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on understanding Modern software engineering concepts & establishing new collaborations in these areas.

The mobile phones are becoming now an irreplaceable utility of every household. It serves as wall clock, alarm clock, calculator, calendar, timer and many more, but have this multi-functionality overloaded the interface of the new generation of the mobile phones. The youth have adapted well to these multiple functionalities graphical user interface, but the interface has now haunting effects for usage by the two age groups i.e. elderly and kids. The interface may end up leading the new generation mobiles in the market useless or of very little use to the elderly and kids. This leads towards the need of age based user interface in the mobile operating system which will consist of interface selection home screen which further directs to age oriented interfaces.

The formal methods community is in general very good at undertaking research into the mathematical aspects of formal methods, but not so good at promulgating the use of formal methods in an engineering environment and at an industrial scale. Technology transfer is an extremely important part of the overall effort necessary in the acceptance of formal techniques. This paper explores some of the more informal aspects of applying formal methods and presents some maxims with associated discussion that may help in the application of formal methods in an industrial setting.

Context: In recent times, many organizations have started using agile software development methodologies instead of using traditional methodologies. The main reason for this shift is the ability of agile approaches to cope with changes in the requirements, customer satisfaction and assurance of on-time delivery of quality products [19]. Test-Driven Development (TDD) is a software development methodology that is considered to be one of the most prominent practices of eXtreme Programming (XP) (an agile methodology) [1][9][10]. Test-list in TDD is considered as a temporary repository in which test items are stored and later by using those items test cases are developed. Requirements Traceability is also a major problem in agile development mainly because of lack of formal requirements specification and frequent requirements change. 
Objectives: This study explores the utilization of test-list and possibility of using test-list for requirements traceability in TDD. This study describes concept of test-list, its formation and exploring its utilization in TDD. Methods for implementing requirements traceability in and identification of possibility of utilizing test-list for requirements traceability in TDD is also explored. 
Methods: Methods used in this study are systematic literature review, surveys and interviews. Systematic literature review was done using seven electronic databases, including Inspec, IEEE Xplore, ACM Digital Library, Springer, Science Direct and Scopus. Studies were selected on the bases of preliminary, basic and advanced developed criteria. Survey was conducted using online questionnaire from TDD practitioners. Findings from literature review and surveys were used to develop interview questionnaires. Interviews were conducted from the same practitioners that were involved in surveys. 
Results: Based on the findings of literature review, questionnaire and interviews, we obtained TDD practices for test-list development and requirements traceability. Analysis was performed on results of SLR and questionnaire and possibility of using test-list for requirements traceability was identified. Based on the analysis of literature review and surveys, interview questionnaire were developed to further investigate the area of interest. We have found that in literature there is no defined method to develop test-list. and survey participants also confirms it. Majority of survey participants create testlist temporarily and informal. On question of whether test-list can be use for requirements traceability around 70% of participants are agree for its use. Interview respondents also confirm the findings of survey. 
Conclusions: Literature has not provided any test-list development method and practitioners also have no clear guideline to develop test-list prior to Test development. Systematic literature review and practitioner’s survey and interviews confirm it. Literature is also silent for any specific requirements change management or requirements traceability method in TDD. We identified requirements traceability practices in agile and management through literature and survey. After analysis of gathered data we found TDD lacks in test-list formalization, none of the study focuses on requirements traceability in TDD. In this study our contribution is exploration of test-list creation and utilization through literature and state of the practice; after practitioners feedback we also explored that test-list can be used for requirements traceability.

Testing is as good as its test cases. It means testing is highly dependent upon faults detection ability of test cases. Test case generation plays a vital role in testing process and is main area of research in the field of software testing. The good test cases decrease the chances of failure of the system and ensure the quality of the system. This paper presents the survey of the various test case generation techniques / methods for object-oriented systems in more comprehensive way.

The International Journal of Software Engineering & Applications (IJSEA) is a bi-monthly open access peer-reviewed journal that publishes articles which contribute new results in all areas of the Software Engineering & Applications. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on understanding Modern software engineering concepts & establishing new collaborations in these areas.

Software testing is a vital and basic movement in developing software that arranges software quality. Nonetheless, the testing procedure is devouring exercises that should be automated to spare a considerable measure of assets. Towards automated testing, computerizing experiments age as the primary testing process is being featured. The huge part of automatic testing methods is that it accelerates the conveyance of administration of the items to the world with little odds of misfortune, and builds the product esteem. In the event that the reason for existing were to diminish the costs and drawing nearer to innovation, at that point testing automation would be a pivotal decision. The objective of this paper is to compare the Genetic and Memetic Algorithm in test case generation from UML diagrams and to optimize the comprehension of UML chart based testing systems.

Number of software Reliability growth models has been proposed in the literature. A mathematical technique which describes the software testing phenomenon known as the software reliability growth model. Software reliability growth models are used to predict the number of faults and reliability of the software. In the view of this software reliability growth models are basically differentiated as the continuous and discrete models. There is a plenty of development in the continuous models but little towards the discrete models. In this paper we have presented a discrete reliability growth model with different discrete testing effort functions and the same time software release policy is discussed. A new imperfect debugging discrete software reliability growth model with testing effort is proposed. All calculations are done on real data. The results shows the proposed testing effort models are perfectly fit to the data.

Effectiveness is important quality factor to testab
ility measurement of object oriented software at an
initial
stage of software development process exclusively a
t design phase for high quality product. It will he
lp
developer’s design capability to achieve the specif
ied functionalities, characteristics, better design
quality
and behavior using appropriate object oriented desi
gn (OOD) concepts and procedures. Metric based
model for ‘Effectiveness Quantification Model of Ob
ject Oriented Design’ has been proposed by
establishing the correlation between effectiveness
and OOD constructs. Later ‘Effectiveness Quantifica
tion
Model’ is empirically validated and statistical sig
nificance of the study considers the high correlati
on for
model acceptance. The aim of this research work is
to encourage researchers and developers for inclusi
on
of the effectiveness quantification model to access
and quantify software effectiveness quality factor
at
design time.

One of the very important aspects of software quality is software testing.
Software testing consumes 30%-50% of the most software projects. Testing
should not only be performed for the quality or development process requirement
but due to the fact that testing needs to ensure that the software performs
what it is supposed to do. UWS has responded to this need of the software testing
in industry by introducing a course on Software Testing- ‘Fundamentals of
Software Testing’ in undergraduate studies. This course is an outcome of strategic
alignment of UWS with Polaris Software Pty Ltd involved in testing of
large software projects. The course aims to prepare students for understanding
of Software Testing Life cycle. This course is jointly delivered by academics
and software testing specialists from industry, to provide a holistic view of
software testing as practiced by the software industry.

The purpose of a metamodel in web engineering methodologies is for the platform independent analysis as well as the design of the content, navigation, and presentation issues of web applications. In the previous years, numbers of methodologies for the development of web applications were proposed, and most of them defined their notation for creating metamodels. The increasing expansion and complexity of web applications are a new challenge for web software developers. This paper presents a comparison study between metamodel of the three methodologies which are; UML-Based Web Engineering (UWE), Web Modeling Language (WebML) and Object Oriented Hypermedia (OOH). The aim is to show the capability of the methodologies to address the challenges in developing the web applications. The evaluation results presented in this paper help the designer in providing initial knowledge of the strengths and weaknesses of the three methodologies for developing web applications.

Today statecharts are a de facto standard in industry for modeling system behavior. Test data generation is one of the key issues in software testing. This paper proposes an reduction approach to test data generation for the state-based software testing. In this paper, first state transition graph is derived from state chart diagram. Then, all the required information are extracted from the state chart diagram. Then, test cases are generated. Lastly, a set of test cases are minimized by calculating the node coverage for each test case. It is also determined that which test cases are covered by other test cases. The advantage of our test generation technique is that it optimizes test coverage by minimizing time and cost. The present test data generation scheme generates test cases which satisfy transition path coverage criteria, path coverage criteria and action coverage criteria. A case study on Railway Ticket Vending Machine (RTVM) has been presented to illustrate our approach.