CINXE.COM

<!DOCTYPE html> <html lang="en" dir="ltr"> <head>  <script async src="https://www.googletagmanager.com/gtag/js?id=G-P63WKM1TM1"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-P63WKM1TM1'); </script>  <script type="text/javascript" > (function(m,e,t,r,i,k,a){m[i]=m[i]||function(){(m[i].a=m[i].a||[]).push(arguments)}; m[i].l=1*new Date(); for (var j = 0; j < document.scripts.length; j++) {if (document.scripts[j].src === r) { return; }} k=e.createElement(t),a=e.getElementsByTagName(t)[0],k.async=1,k.src=r,a.parentNode.insertBefore(k,a)}) (window, document, "script", "https://mc.yandex.ru/metrika/tag.js", "ym"); ym(55165297, "init", { clickmap:false, trackLinks:true, accurateTrackBounce:true, webvisor:false }); </script> <noscript><div><img src="https://mc.yandex.ru/watch/55165297" style="position:absolute; left:-9999px;" alt="" /></div></noscript>    <title>Search results for: software testing techniques</title> <meta name="description" content="Search results for: software testing techniques"> <meta name="keywords" content="software testing techniques"> <meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1, maximum-scale=1, user-scalable=no"> <meta charset="utf-8"> <link href="https://cdn.waset.org/favicon.ico" type="image/x-icon" rel="shortcut icon"> <link href="https://cdn.waset.org/static/plugins/bootstrap-4.2.1/css/bootstrap.min.css" rel="stylesheet"> <link href="https://cdn.waset.org/static/plugins/fontawesome/css/all.min.css" rel="stylesheet"> <link href="https://cdn.waset.org/static/css/site.css?v=150220211555" rel="stylesheet"> </head> <body> <header> <div class="container"> <nav class="navbar navbar-expand-lg navbar-light"> <a class="navbar-brand" href="https://waset.org"> <img src="https://cdn.waset.org/static/images/wasetc.png" alt="Open Science Research Excellence" title="Open Science Research Excellence" /> </a> <button class="d-block d-lg-none navbar-toggler ml-auto" type="button" data-toggle="collapse" data-target="#navbarMenu" aria-controls="navbarMenu" aria-expanded="false" aria-label="Toggle navigation"> <span class="navbar-toggler-icon"></span> </button> <div class="w-100"> <div class="d-none d-lg-flex flex-row-reverse"> <form method="get" action="https://waset.org/search" class="form-inline my-2 my-lg-0"> <input class="form-control mr-sm-2" type="search" placeholder="Search Conferences" value="software testing techniques" name="q" aria-label="Search"> <button class="btn btn-light my-2 my-sm-0" type="submit"><i class="fas fa-search"></i></button> </form> </div> <div class="collapse navbar-collapse mt-1" id="navbarMenu"> <ul class="navbar-nav ml-auto align-items-center" id="mainNavMenu"> <li class="nav-item"> <a class="nav-link" href="https://waset.org/conferences" title="Conferences in 2024/2025/2026">Conferences</a> </li> <li class="nav-item"> <a class="nav-link" href="https://waset.org/disciplines" title="Disciplines">Disciplines</a> </li> <li class="nav-item"> <a class="nav-link" href="https://waset.org/committees" rel="nofollow">Committees</a> </li> <li class="nav-item dropdown"> <a class="nav-link dropdown-toggle" href="#" id="navbarDropdownPublications" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Publications </a> <div class="dropdown-menu" aria-labelledby="navbarDropdownPublications"> <a class="dropdown-item" href="https://publications.waset.org/abstracts">Abstracts</a> <a class="dropdown-item" href="https://publications.waset.org">Periodicals</a> <a class="dropdown-item" href="https://publications.waset.org/archive">Archive</a> </div> </li> <li class="nav-item"> <a class="nav-link" href="https://waset.org/page/support" title="Support">Support</a> </li> </ul> </div> </div> </nav> </div> </header> <main> <div class="container mt-4"> <div class="row"> <div class="col-md-9 mx-auto"> <form method="get" action="https://publications.waset.org/abstracts/search"> <div id="custom-search-input"> <div class="input-group"> <i class="fas fa-search"></i> <input type="text" class="search-query" name="q" placeholder="Author, Title, Abstract, Keywords" value="software testing techniques"> <input type="submit" class="btn_search" value="Search"> </div> </div> </form> </div> </div> <div class="row mt-3"> <div class="col-sm-3"> <div class="card"> <div class="card-body"><strong>Commenced</strong> in January 2007</div> </div> </div> <div class="col-sm-3"> <div class="card"> <div class="card-body"><strong>Frequency:</strong> Monthly</div> </div> </div> <div class="col-sm-3"> <div class="card"> <div class="card-body"><strong>Edition:</strong> International</div> </div> </div> <div class="col-sm-3"> <div class="card"> <div class="card-body"><strong>Paper Count:</strong> 13501</div> </div> </div> </div> <h1 class="mt-3 mb-3 text-center" style="font-size:1.6rem;">Search results for: software testing techniques</h1> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13501</span> Analyzing the Effectiveness of Different Testing Techniques in Ensuring Software Quality</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=R.%20M.%20P.%20C.%20Bandara">R. M. P. C. Bandara</a>, <a href="https://publications.waset.org/abstracts/search?q=M.%20L.%20L.%20Weerasinghe"> M. L. L. Weerasinghe</a>, <a href="https://publications.waset.org/abstracts/search?q=K.%20T.%20C.%20R.%20Kumari"> K. T. C. R. Kumari</a>, <a href="https://publications.waset.org/abstracts/search?q=A.%20G.%20D.%20R.%20Hansika"> A. G. D. R. Hansika</a>, <a href="https://publications.waset.org/abstracts/search?q=D.%20I.%20De%20Silva"> D. I. De Silva</a>, <a href="https://publications.waset.org/abstracts/search?q=D.%20M.%20T.%20H.%20Dias"> D. M. T. H. Dias</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software testing is an essential process in software development that aims to identify defects and ensure that software is functioning as intended. Various testing techniques are employed to achieve this goal, but the effectiveness of these techniques varies. This research paper analyzes the effectiveness of different testing techniques in ensuring software quality. The paper explores different testing techniques, including manual and automated testing, and evaluates their effectiveness in terms of identifying defects, reducing the number of defects in software, and ensuring that software meets its functional and non-functional requirements. Moreover, the paper will also investigate the impact of factors such as testing time, test coverage, and testing environment on the effectiveness of these techniques. This research aims to provide valuable insights into the effectiveness of different testing techniques, enabling software development teams to make informed decisions about the testing approach that is best suited to their needs. By improving testing techniques, the number of defects in software can be reduced, enhancing the quality of software and ultimately providing better software for users. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20testing%20life%20cycle" title="software testing life cycle">software testing life cycle</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques" title=" software testing techniques"> software testing techniques</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing%20strategies" title=" software testing strategies"> software testing strategies</a>, <a href="https://publications.waset.org/abstracts/search?q=effectiveness" title=" effectiveness"> effectiveness</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20quality" title=" software quality"> software quality</a> </p> <a href="https://publications.waset.org/abstracts/166772/analyzing-the-effectiveness-of-different-testing-techniques-in-ensuring-software-quality" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/166772.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">84</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13500</span> Automated Java Testing: JUnit versus AspectJ</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Manish%20Jain">Manish Jain</a>, <a href="https://publications.waset.org/abstracts/search?q=Dinesh%20Gopalani"> Dinesh Gopalani</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Growing dependency of mankind on software technology increases the need for thorough testing of the software applications and automated testing techniques that support testing activities. We have outlined our testing strategy for performing various types of automated testing of Java applications using AspectJ which has become the de-facto standard for Aspect Oriented Programming (AOP). Likewise JUnit, a unit testing framework is the most popular Java testing tool. In this paper, we have evaluated our proposed AOP approach for automated testing and JUnit on various parameters. First we have provided the similarity between the two approaches and then we have done a detailed comparison of the two testing techniques on factors like lines of testing code, learning curve, testing of private members etc. We established that our AOP testing approach using AspectJ has got several advantages and is thus particularly more effective than JUnit. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=aspect%20oriented%20programming" title="aspect oriented programming">aspect oriented programming</a>, <a href="https://publications.waset.org/abstracts/search?q=AspectJ" title=" AspectJ"> AspectJ</a>, <a href="https://publications.waset.org/abstracts/search?q=aspects" title=" aspects"> aspects</a>, <a href="https://publications.waset.org/abstracts/search?q=JU-nit" title=" JU-nit"> JU-nit</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a> </p> <a href="https://publications.waset.org/abstracts/82341/automated-java-testing-junit-versus-aspectj" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/82341.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">331</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13499</span> Determining the Most Efficient Test Available in Software Testing</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Qasim%20Zafar">Qasim Zafar</a>, <a href="https://publications.waset.org/abstracts/search?q=Matthew%20Anderson"> Matthew Anderson</a>, <a href="https://publications.waset.org/abstracts/search?q=Esteban%20Garcia"> Esteban Garcia</a>, <a href="https://publications.waset.org/abstracts/search?q=Steven%20Drager"> Steven Drager</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software failures can present an enormous detriment to people's lives and cost millions of dollars to repair when they are unexpectedly encountered in the wild. Despite a significant portion of the software development lifecycle and resources are dedicated to testing, software failures are a relatively frequent occurrence. Nevertheless, the evaluation of testing effectiveness remains at the forefront of ensuring high-quality software and software metrics play a critical role in providing valuable insights into quantifiable objectives to assess the level of assurance and confidence in the system. As the selection of appropriate metrics can be an arduous process, the goal of this paper is to shed light on the significance of software metrics by examining a range of testing techniques and metrics as well as identifying key areas for improvement. Additionally, through this investigation, readers will gain a deeper understanding of how metrics can help to drive informed decision-making on delivering high-quality software and facilitate continuous improvement in testing practices. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title="software testing">software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20metrics" title=" software metrics"> software metrics</a>, <a href="https://publications.waset.org/abstracts/search?q=testing%20effectiveness" title=" testing effectiveness"> testing effectiveness</a>, <a href="https://publications.waset.org/abstracts/search?q=black%20box%20testing" title=" black box testing"> black box testing</a>, <a href="https://publications.waset.org/abstracts/search?q=random%20testing" title=" random testing"> random testing</a>, <a href="https://publications.waset.org/abstracts/search?q=adaptive%20random%20testing" title=" adaptive random testing"> adaptive random testing</a>, <a href="https://publications.waset.org/abstracts/search?q=combinatorial%20testing" title=" combinatorial testing"> combinatorial testing</a>, <a href="https://publications.waset.org/abstracts/search?q=fuzz%20testing" title=" fuzz testing"> fuzz testing</a>, <a href="https://publications.waset.org/abstracts/search?q=equivalence%20partition" title=" equivalence partition"> equivalence partition</a>, <a href="https://publications.waset.org/abstracts/search?q=boundary%20value%20analysis" title=" boundary value analysis"> boundary value analysis</a>, <a href="https://publications.waset.org/abstracts/search?q=white%20box%20testing" title=" white box testing"> white box testing</a> </p> <a href="https://publications.waset.org/abstracts/169666/determining-the-most-efficient-test-available-in-software-testing" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/169666.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">89</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13498</span> Analyzing Test Data Generation Techniques Using Evolutionary Algorithms</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Arslan%20Ellahi">Arslan Ellahi</a>, <a href="https://publications.waset.org/abstracts/search?q=Syed%20Amjad%20Hussain"> Syed Amjad Hussain</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software Testing is a vital process in software development life cycle. We can attain the quality of software after passing it through software testing phase. We have tried to find out automatic test data generation techniques that are a key research area of software testing to achieve test automation that can eventually decrease testing time. In this paper, we review some of the approaches presented in the literature which use evolutionary search based algorithms like Genetic Algorithm, Particle Swarm Optimization (PSO), etc. to validate the test data generation process. We also look into the quality of test data generation which increases or decreases the efficiency of testing. We have proposed test data generation techniques for model-based testing. We have worked on tuning and fitness function of PSO algorithm. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=search%20based" title="search based">search based</a>, <a href="https://publications.waset.org/abstracts/search?q=evolutionary%20algorithm" title=" evolutionary algorithm"> evolutionary algorithm</a>, <a href="https://publications.waset.org/abstracts/search?q=particle%20swarm%20optimization" title=" particle swarm optimization"> particle swarm optimization</a>, <a href="https://publications.waset.org/abstracts/search?q=genetic%20algorithm" title=" genetic algorithm"> genetic algorithm</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20data%20generation" title=" test data generation"> test data generation</a> </p> <a href="https://publications.waset.org/abstracts/92727/analyzing-test-data-generation-techniques-using-evolutionary-algorithms" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/92727.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">189</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13497</span> Analyzing Software Testing Phase in Agile Project Management: The Case of Jordan</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ghaleb%20Y.%20Abbasi">Ghaleb Y. Abbasi</a>, <a href="https://publications.waset.org/abstracts/search?q=Satanay%20Alhiary"> Satanay Alhiary</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper focused on software testing phase of activities, types, techniques, teams and methods under agile project management (APM) in the Jordanian software industry. The effect of using agile principles and practices on testing process in software development life cycle (SDLC) was analyzed in order to create full view of the agile testing aspects such as phases, levels, types, methods, team and customers. Qualitative and quantitative research methods were utilized to cover earlier literature and collect data via web survey and short interviews in Jordanian software companies. Results indicated that agile testing had positive influence on quality of product, team performance, and customer satisfaction with a rate above 80%. APM is a powerful practice of moving software project forward in current markets with a rate above 51% by early involvement of testing activities in development. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=agile%20project%20management" title="agile project management">agile project management</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20development%20life%20cycle" title=" software development life cycle"> software development life cycle</a>, <a href="https://publications.waset.org/abstracts/search?q=agile%20methods" title=" agile methods"> agile methods</a>, <a href="https://publications.waset.org/abstracts/search?q=agile%20testing" title=" agile testing"> agile testing</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a> </p> <a href="https://publications.waset.org/abstracts/60185/analyzing-software-testing-phase-in-agile-project-management-the-case-of-jordan" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/60185.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">456</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13496</span> Quality and Coverage Assessment in Software Integration Based On Mutation Testing</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Iyad%20Alazzam">Iyad Alazzam</a>, <a href="https://publications.waset.org/abstracts/search?q=Kenneth%20Magel"> Kenneth Magel</a>, <a href="https://publications.waset.org/abstracts/search?q=Izzat%20Alsmadi"> Izzat Alsmadi</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The different activities and approaches in software testing try to find the most possible number of errors or failures with the least amount of possible effort. Mutation is a testing approach that is used to discover possible errors in tested applications. This is accomplished through changing one aspect of the software from its original and writes test cases to detect such change or mutation. In this paper, we present a mutation approach for testing software components integration aspects. Several mutation operations related to components integration are described and evaluated. A test case study of several open source code projects is collected. Proposed mutation operators are applied and evaluated. Results showed some insights and information that can help testing activities in detecting errors and improving coverage. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title="software testing">software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=integration%20testing" title=" integration testing"> integration testing</a>, <a href="https://publications.waset.org/abstracts/search?q=mutation" title=" mutation"> mutation</a>, <a href="https://publications.waset.org/abstracts/search?q=coverage" title=" coverage"> coverage</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20design" title=" software design"> software design</a> </p> <a href="https://publications.waset.org/abstracts/5230/quality-and-coverage-assessment-in-software-integration-based-on-mutation-testing" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/5230.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">427</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13495</span> A Comparative Study of Three Major Performance Testing Tools</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Abdulaziz%20Omar%20Alsadhan">Abdulaziz Omar Alsadhan</a>, <a href="https://publications.waset.org/abstracts/search?q=Mohd%20Mudasir%20Shafi"> Mohd Mudasir Shafi</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Performance testing is done to prove the reliability of any software product. There are a number of tools available in the markets that are used to perform performance testing. In this paper we present a comparative study of the three most commonly used performance testing tools. These tools cover the major share of the performance testing market and are widely used. In this paper we compared the tools on five evaluation parameters which are; User friendliness, portability, tool support, compatibility and cost. The conclusion provided at the end of the paper is based on our study and does not support any tool or company. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20development" title="software development">software development</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=quality%20assurance" title=" quality assurance"> quality assurance</a>, <a href="https://publications.waset.org/abstracts/search?q=performance%20testing" title=" performance testing"> performance testing</a>, <a href="https://publications.waset.org/abstracts/search?q=load%20runner" title=" load runner"> load runner</a>, <a href="https://publications.waset.org/abstracts/search?q=rational%20testing" title=" rational testing"> rational testing</a>, <a href="https://publications.waset.org/abstracts/search?q=silk%20performer" title=" silk performer"> silk performer</a> </p> <a href="https://publications.waset.org/abstracts/4106/a-comparative-study-of-three-major-performance-testing-tools" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/4106.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">607</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13494</span> A New Approach for Assertions Processing during Assertion-Based Software Testing</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ali%20M.%20Alakeel">Ali M. Alakeel</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Assertion-based software testing has been shown to be a promising tool for generating test cases that reveal program faults. Because the number of assertions may be very large for industry-size programs, one of the main concerns to the applicability of assertion-based testing is the amount of search time required to explore a large number of assertions. This paper presents a new approach for assertions exploration during the process of Assertion-Based software testing. Our initial exterminations with the proposed approach show that the performance of Assertion-Based testing may be improved, therefore, making this approach more efficient when applied on programs with large number of assertions. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title="software testing">software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=assertion-based%20testing" title=" assertion-based testing"> assertion-based testing</a>, <a href="https://publications.waset.org/abstracts/search?q=program%20assertions" title=" program assertions"> program assertions</a>, <a href="https://publications.waset.org/abstracts/search?q=generating%20test" title=" generating test"> generating test</a> </p> <a href="https://publications.waset.org/abstracts/18643/a-new-approach-for-assertions-processing-during-assertion-based-software-testing" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/18643.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">460</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13493</span> Drive Sharing with Multimodal Interaction: Enhancing Safety and Efficiency</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Sagar%20Jitendra%20Mahendrakar">Sagar Jitendra Mahendrakar</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Exploratory testing is a dynamic and adaptable method of software quality assurance that is frequently praised for its ability to find hidden flaws and improve the overall quality of the product. Instead of using preset test cases, exploratory testing allows testers to explore the software application dynamically. This is in contrast to scripted testing methodologies, which primarily rely on tester intuition, creativity, and adaptability. There are several tools and techniques that can aid testers in the exploratory testing process which we will be discussing in this talk.Tests of this kind are able to find bugs of this kind that are harder to find during structured testing or that other testing methods may have overlooked.The purpose of this abstract is to examine the nature and importance of exploratory testing in modern software development methods. It explores the fundamental ideas of exploratory testing, highlighting the value of domain knowledge and tester experience in spotting possible problems that may escape the notice of traditional testing methodologies. Throughout the software development lifecycle, exploratory testing promotes quick feedback loops and continuous improvement by giving testers the ability to make decisions in real time based on their observations. This abstract also clarifies the unique features of exploratory testing, like its non-linearity and capacity to replicate user behavior in real-world settings. Testers can find intricate bugs, usability problems, and edge cases in software through impromptu exploration that might go undetected. Exploratory testing's flexible and iterative structure fits in well with agile and DevOps processes, allowing for a quicker time to market without sacrificing the quality of the final product. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=exploratory" title="exploratory">exploratory</a>, <a href="https://publications.waset.org/abstracts/search?q=testing" title=" testing"> testing</a>, <a href="https://publications.waset.org/abstracts/search?q=automation" title=" automation"> automation</a>, <a href="https://publications.waset.org/abstracts/search?q=quality" title=" quality"> quality</a> </p> <a href="https://publications.waset.org/abstracts/186417/drive-sharing-with-multimodal-interaction-enhancing-safety-and-efficiency" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/186417.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">51</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13492</span> CompleX-Machine: An Automated Testing Tool Using X-Machine Theory</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=E.%20K.%20A.%20Ogunshile">E. K. A. Ogunshile</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper is aimed at creating an Automatic Java X-Machine testing tool for software development. The nature of software development is changing; thus, the type of software testing tools required is also changing. Software is growing increasingly complex and, in part due to commercial impetus for faster software releases with new features and value, increasingly in danger of containing faults. These faults can incur huge cost for software development organisations and users; Cambridge Judge Business School’s research estimated the cost of software bugs to the global economy is $312 billion. Beyond the cost, faster software development methodologies and increasing expectations on developers to become testers is driving demand for faster, automated, and effective tools to prevent potential faults as early as possible in the software development lifecycle. Using X-Machine theory, this paper will explore a new tool to address software complexity, changing expectations on developers, faster development pressures and methodologies, with a view to reducing the huge cost of fixing software bugs. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=conformance%20testing" title="conformance testing">conformance testing</a>, <a href="https://publications.waset.org/abstracts/search?q=finite%20state%20machine" title=" finite state machine"> finite state machine</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=x-machine" title=" x-machine"> x-machine</a> </p> <a href="https://publications.waset.org/abstracts/82574/complex-machine-an-automated-testing-tool-using-x-machine-theory" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/82574.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">268</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13491</span> JavaScript Object Notation Data against eXtensible Markup Language Data in Software Applications a Software Testing Approach</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Theertha%20Chandroth">Theertha Chandroth</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper presents a comparative study on how to check JSON (JavaScript Object Notation) data against XML (eXtensible Markup Language) data from a software testing point of view. JSON and XML are widely used data interchange formats, each with its unique syntax and structure. The objective is to explore various techniques and methodologies for validating comparison and integration between JSON data to XML and vice versa. By understanding the process of checking JSON data against XML data, testers, developers and data practitioners can ensure accurate data representation, seamless data interchange, and effective data validation. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=XML" title="XML">XML</a>, <a href="https://publications.waset.org/abstracts/search?q=JSON" title=" JSON"> JSON</a>, <a href="https://publications.waset.org/abstracts/search?q=data%20comparison" title=" data comparison"> data comparison</a>, <a href="https://publications.waset.org/abstracts/search?q=integration%20testing" title=" integration testing"> integration testing</a>, <a href="https://publications.waset.org/abstracts/search?q=Python" title=" Python"> Python</a>, <a href="https://publications.waset.org/abstracts/search?q=SQL" title=" SQL"> SQL</a> </p> <a href="https://publications.waset.org/abstracts/170435/javascript-object-notation-data-against-extensible-markup-language-data-in-software-applications-a-software-testing-approach" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/170435.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">140</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13490</span> Graphical User Interface Testing by Using Deep Learning</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Akshat%20Mathur">Akshat Mathur</a>, <a href="https://publications.waset.org/abstracts/search?q=Sunil%20Kumar%20Khatri"> Sunil Kumar Khatri</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper presents brief about how the use of Artificial intelligence in respect to GUI testing can reduce workload by using DL-fueled method. This paper also discusses about how graphical user interface and event driven software testing can derive benefits from the use of AI techniques. The use of AI techniques not only reduces the task and work load but also helps in getting better output than manual testing. Although results are same, but the use of Artifical intelligence techniques for GUI testing has proven to provide ideal results. DL-fueled framework helped us to find imperfections of the entire webpage and provides test failure result in a score format between 0 and 1which signifies that are test meets it quality criteria or not. This paper proposes DL-fueled method which helps us to find the genuine GUI bugs and defects and also helped us to scale the existing labour-intensive and skill-intensive methodologies. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=graphical%20user%20interface" title="graphical user interface">graphical user interface</a>, <a href="https://publications.waset.org/abstracts/search?q=GUI" title=" GUI"> GUI</a>, <a href="https://publications.waset.org/abstracts/search?q=artificial%20intelligence" title=" artificial intelligence"> artificial intelligence</a>, <a href="https://publications.waset.org/abstracts/search?q=deep%20learning" title=" deep learning"> deep learning</a>, <a href="https://publications.waset.org/abstracts/search?q=ML%20technology" title=" ML technology"> ML technology</a> </p> <a href="https://publications.waset.org/abstracts/104062/graphical-user-interface-testing-by-using-deep-learning" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/104062.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">177</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13489</span> The Effect of Program Type on Mutation Testing: Comparative Study</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=B.%20Falah">B. Falah</a>, <a href="https://publications.waset.org/abstracts/search?q=N.%20E.%20Abakouy"> N. E. Abakouy</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Due to its high computational cost, mutation testing has been neglected by researchers. Recently, many cost and mutants’ reduction techniques have been developed, improved, and experimented, but few of them has relied the possibility of reducing the cost of mutation testing on the program type of the application under test. This paper is a comparative study between four operators’ selection techniques (mutants sampling, class level operators, method level operators, and all operators’ selection) based on the program code type of each application under test. It aims at finding an alternative approach to reveal the effect of code type on mutation testing score. The result of our experiment shows that the program code type can affect the mutation score and that the programs using polymorphism are best suited to be tested with mutation testing. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=equivalent%20mutant" title="equivalent mutant">equivalent mutant</a>, <a href="https://publications.waset.org/abstracts/search?q=killed%20mutant" title=" killed mutant"> killed mutant</a>, <a href="https://publications.waset.org/abstracts/search?q=mutation%20score" title=" mutation score"> mutation score</a>, <a href="https://publications.waset.org/abstracts/search?q=mutation%20testing" title=" mutation testing"> mutation testing</a>, <a href="https://publications.waset.org/abstracts/search?q=program%20code%20type" title=" program code type"> program code type</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a> </p> <a href="https://publications.waset.org/abstracts/34959/the-effect-of-program-type-on-mutation-testing-comparative-study" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/34959.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">554</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13488</span> [Keynote Talk]: Software Reliability Assessment and Fault Tolerance: Issues and Challenges</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=T.%20Gayen">T. Gayen</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Although, there are several software reliability models existing today there does not exist any versatile model even today which can be used for the reliability assessment of software. Complex software has a large number of states (unlike the hardware) so it becomes practically difficult to completely test the software. Irrespective of the amount of testing one does, sometimes it becomes extremely difficult to assure that the final software product is fault free. The Black Box Software Reliability models are found be quite uncertain for the reliability assessment of various systems. As mission critical applications need to be highly reliable and since it is not always possible to ensure the development of highly reliable system. Hence, in order to achieve fault-free operation of software one develops some mechanism to handle faults remaining in the system even after the development. Although, several such techniques are currently in use to achieve fault tolerance, yet these mechanisms may not always be very suitable for various systems. Hence, this discussion is focused on analyzing the issues and challenges faced with the existing techniques for reliability assessment and fault tolerance of various software systems. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=black%20box" title="black box">black box</a>, <a href="https://publications.waset.org/abstracts/search?q=fault%20tolerance" title=" fault tolerance"> fault tolerance</a>, <a href="https://publications.waset.org/abstracts/search?q=failure" title=" failure"> failure</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20reliability" title=" software reliability"> software reliability</a> </p> <a href="https://publications.waset.org/abstracts/47523/keynote-talk-software-reliability-assessment-and-fault-tolerance-issues-and-challenges" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/47523.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">426</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13487</span> Comparative Analysis of Automation Testing Tools</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Amit%20Bhanushali">Amit Bhanushali</a> </p> <p class="card-text"><strong>Abstract:</strong></p> In the ever-changing landscape of software development, automated software testing has emerged as a critical component of the Software Development Life Cycle (SDLC). This research undertakes a comparative study of three major automated testing tools -UFT, Selenium, and RPA- evaluating them on usability, maintenance, and effectiveness. Leveraging existing JAVA-based applications as test cases, the study aims to guide testers in selecting the optimal tool for specific applications. By exploring key features such as source and licensing, testing expenses, object repositories, usability, and language support, the research provides practical insights into UFT, Selenium, and RPA. Acknowledging the pivotal role of these tools in streamlining testing processes amid time constraints and resource limitations, the study assists professionals in making informed choices aligned with their organizational needs. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20testing%20tools" title="software testing tools">software testing tools</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20development%20lifecycle%20%28SDLC%29" title=" software development lifecycle (SDLC)"> software development lifecycle (SDLC)</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20automation%20frameworks" title=" test automation frameworks"> test automation frameworks</a>, <a href="https://publications.waset.org/abstracts/search?q=automated%20software" title=" automated software"> automated software</a>, <a href="https://publications.waset.org/abstracts/search?q=JAVA-based" title=" JAVA-based"> JAVA-based</a>, <a href="https://publications.waset.org/abstracts/search?q=UFT" title=" UFT"> UFT</a>, <a href="https://publications.waset.org/abstracts/search?q=selenium%20and%20RPA%20%28robotic%20process%20automation%29" title=" selenium and RPA (robotic process automation)"> selenium and RPA (robotic process automation)</a>, <a href="https://publications.waset.org/abstracts/search?q=source%20and%20licensing" title=" source and licensing"> source and licensing</a>, <a href="https://publications.waset.org/abstracts/search?q=object%20repository" title=" object repository"> object repository</a> </p> <a href="https://publications.waset.org/abstracts/173823/comparative-analysis-of-automation-testing-tools" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/173823.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">97</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13486</span> A Multi-Release Software Reliability Growth Models Incorporating Imperfect Debugging and Change-Point under the Simulated Testing Environment and Software Release Time</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Sujit%20Kumar%20Pradhan">Sujit Kumar Pradhan</a>, <a href="https://publications.waset.org/abstracts/search?q=Anil%20Kumar"> Anil Kumar</a>, <a href="https://publications.waset.org/abstracts/search?q=Vijay%20Kumar"> Vijay Kumar</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The testing process of the software during the software development time is a crucial step as it makes the software more efficient and dependable. To estimate software’s reliability through the mean value function, many software reliability growth models (SRGMs) were developed under the assumption that operating and testing environments are the same. Practically, it is not true because when the software works in a natural field environment, the reliability of the software differs. This article discussed an SRGM comprising change-point and imperfect debugging in a simulated testing environment. Later on, we extended it in a multi-release direction. Initially, the software was released to the market with few features. According to the market’s demand, the software company upgraded the current version by adding new features as time passed. Therefore, we have proposed a generalized multi-release SRGM where change-point and imperfect debugging concepts have been addressed in a simulated testing environment. The failure-increasing rate concept has been adopted to determine the change point for each software release. Based on nine goodness-of-fit criteria, the proposed model is validated on two real datasets. The results demonstrate that the proposed model fits the datasets better. We have also discussed the optimal release time of the software through a cost model by assuming that the testing and debugging costs are time-dependent. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20reliability%20growth%20models" title="software reliability growth models">software reliability growth models</a>, <a href="https://publications.waset.org/abstracts/search?q=non-homogeneous%20Poisson%20process" title=" non-homogeneous Poisson process"> non-homogeneous Poisson process</a>, <a href="https://publications.waset.org/abstracts/search?q=multi-release%20software" title=" multi-release software"> multi-release software</a>, <a href="https://publications.waset.org/abstracts/search?q=mean%20value%20function" title=" mean value function"> mean value function</a>, <a href="https://publications.waset.org/abstracts/search?q=change-point" title=" change-point"> change-point</a>, <a href="https://publications.waset.org/abstracts/search?q=environmental%20factors" title=" environmental factors"> environmental factors</a> </p> <a href="https://publications.waset.org/abstracts/172552/a-multi-release-software-reliability-growth-models-incorporating-imperfect-debugging-and-change-point-under-the-simulated-testing-environment-and-software-release-time" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/172552.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">74</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13485</span> Experience Report about the Inclusion of People with Disabilities in the Process of Testing an Accessible System for Learning Management</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Marcos%20Devaner">Marcos Devaner</a>, <a href="https://publications.waset.org/abstracts/search?q=Marcela%20Alves"> Marcela Alves</a>, <a href="https://publications.waset.org/abstracts/search?q=Cledson%20Braga"> Cledson Braga</a>, <a href="https://publications.waset.org/abstracts/search?q=Fabiano%20Alves"> Fabiano Alves</a>, <a href="https://publications.waset.org/abstracts/search?q=Wilton%20Bezerra"> Wilton Bezerra</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This article discusses the inclusion of people with disabilities in the process of testing an accessible system solution for distance education. The accessible system, team profile, methodologies and techniques covered in the testing process are presented. The testing process shown in this paper was designed from the experience with user. The testing process emerged from lessons learned from past experiences and the end user is present at all stages of the tests. Also, lessons learned are reported and how it was possible the maturing of the team and the methods resulting in a simple, productive and effective process. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=experience%20report" title="experience report">experience report</a>, <a href="https://publications.waset.org/abstracts/search?q=accessible%20systems" title=" accessible systems"> accessible systems</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=testing%20process" title=" testing process"> testing process</a>, <a href="https://publications.waset.org/abstracts/search?q=systems" title=" systems"> systems</a>, <a href="https://publications.waset.org/abstracts/search?q=e-learning" title=" e-learning"> e-learning</a> </p> <a href="https://publications.waset.org/abstracts/47036/experience-report-about-the-inclusion-of-people-with-disabilities-in-the-process-of-testing-an-accessible-system-for-learning-management" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/47036.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">396</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13484</span> Optimization and Automation of Functional Testing with White-Box Testing Method</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Reyhaneh%20Soltanshah">Reyhaneh Soltanshah</a>, <a href="https://publications.waset.org/abstracts/search?q=Hamid%20R.%20Zarandi"> Hamid R. Zarandi</a> </p> <p class="card-text"><strong>Abstract:</strong></p> In order to be more efficient in industries that are related to computer systems, software testing is necessary despite spending time and money. In the embedded system software test, complete knowledge of the embedded system architecture is necessary to avoid significant costs and damages. Software tests increase the price of the final product. The aim of this article is to provide a method to reduce time and cost in tests based on program structure. First, a complete review of eleven white box test methods based on ISO/IEC/IEEE 29119 2015 and 2021 versions has been done. The proposed algorithm is designed using two versions of the 29119 standards, and some white-box testing methods that are expensive or have little coverage have been removed. On each of the functions, white box test methods were applied according to the 29119 standard and then the proposed algorithm was implemented on the functions. To speed up the implementation of the proposed method, the Unity framework has been used with some changes. Unity framework can be used in embedded software testing due to its open source and ability to implement white box test methods. The test items obtained from these two approaches were evaluated using a mathematical ratio, which in various software mining reduced between 50% and 80% of the test cost and reached the desired result with the minimum number of test items. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=embedded%20software" title="embedded software">embedded software</a>, <a href="https://publications.waset.org/abstracts/search?q=reduce%20costs" title=" reduce costs"> reduce costs</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=white-box%20testing" title=" white-box testing"> white-box testing</a> </p> <a href="https://publications.waset.org/abstracts/186100/optimization-and-automation-of-functional-testing-with-white-box-testing-method" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/186100.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">54</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13483</span> Test Suite Optimization Using an Effective Meta-Heuristic BAT Algorithm</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Anuradha%20Chug">Anuradha Chug</a>, <a href="https://publications.waset.org/abstracts/search?q=Sunali%20Gandhi"> Sunali Gandhi</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Regression Testing is a very expensive and time-consuming process carried out to ensure the validity of modified software. Due to the availability of insufficient resources to re-execute all the test cases in time constrained environment, efforts are going on to generate test data automatically without human efforts. Many search based techniques have been proposed to generate efficient, effective as well as optimized test data, so that the overall cost of the software testing can be minimized. The generated test data should be able to uncover all potential lapses that exist in the software or product. Inspired from the natural behavior of bat for searching her food sources, current study employed a meta-heuristic, search-based bat algorithm for optimizing the test data on the basis certain parameters without compromising their effectiveness. Mathematical functions are also applied that can effectively filter out the redundant test data. As many as 50 Java programs are used to check the effectiveness of proposed test data generation and it has been found that 86% saving in testing efforts can be achieved using bat algorithm while covering 100% of the software code for testing. Bat algorithm was found to be more efficient in terms of simplicity and flexibility when the results were compared with another nature inspired algorithms such as Firefly Algorithm (FA), Hill Climbing Algorithm (HC) and Ant Colony Optimization (ACO). The output of this study would be useful to testers as they can achieve 100% path coverage for testing with minimum number of test cases. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=regression%20testing" title="regression testing">regression testing</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20case%20selection" title=" test case selection"> test case selection</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20case%20prioritization" title=" test case prioritization"> test case prioritization</a>, <a href="https://publications.waset.org/abstracts/search?q=genetic%20algorithm" title=" genetic algorithm"> genetic algorithm</a>, <a href="https://publications.waset.org/abstracts/search?q=bat%20algorithm" title=" bat algorithm"> bat algorithm</a> </p> <a href="https://publications.waset.org/abstracts/55510/test-suite-optimization-using-an-effective-meta-heuristic-bat-algorithm" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/55510.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">380</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13482</span> Manual to Automated Testing: An Effort-Based Approach for Determining the Priority of Software Test Automation</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Peter%20Sabev">Peter Sabev</a>, <a href="https://publications.waset.org/abstracts/search?q=Katalina%20Grigorova"> Katalina Grigorova</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Test automation allows performing difficult and time consuming manual software testing tasks efficiently, quickly and repeatedly. However, development and maintenance of automated tests is expensive, so it needs a proper prioritization what to automate first. This paper describes a simple yet efficient approach for such prioritization of test cases based on the effort needed for both manual execution and software test automation. The suggested approach is very flexible because it allows working with a variety of assessment methods, and adding or removing new candidates at any time. The theoretical ideas presented in this article have been successfully applied in real world situations in several software companies by the authors and their colleagues including testing of real estate websites, cryptographic and authentication solutions, OSGi-based middleware framework that has been applied in various systems for smart homes, connected cars, production plants, sensors, home appliances, car head units and engine control units (ECU), vending machines, medical devices, industry equipment and other devices that either contain or are connected to an embedded service gateway. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=automated%20testing" title="automated testing">automated testing</a>, <a href="https://publications.waset.org/abstracts/search?q=manual%20testing" title=" manual testing"> manual testing</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20automation" title=" test automation"> test automation</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20prioritization" title=" test prioritization"> test prioritization</a> </p> <a href="https://publications.waset.org/abstracts/40860/manual-to-automated-testing-an-effort-based-approach-for-determining-the-priority-of-software-test-automation" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/40860.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">335</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13481</span> A Framework for Automating Software Testing: A Practical Approach</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ana%20Paula%20Cavalcanti%20Furtado">Ana Paula Cavalcanti Furtado</a>, <a href="https://publications.waset.org/abstracts/search?q=Silvio%20Meira"> Silvio Meira</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Context: The quality of a software product can be directly influenced by the quality of its development process. Therefore, immature or ad-hoc test processes are means that are unsuited for introducing systematic test automation, and should not be used to support improving the quality of software. Objective: In order to conduct this research, the benefits and limitations of and gaps in automating software testing had to be assessed in order to identify the best practices and to propose a strategy for systematically introducing test automation into software development processes. Method: To conduct this research, an exploratory bibliographical survey was undertaken so as to underpin the search by theory and the recent literature. After defining the proposal, two case studies were conducted so as to analyze the proposal in a real-world environment. In addition, the proposal was also assessed through a focus group with specialists in the field. Results: The proposal of a Framework for Automating Software Testing (FAST), which is a theoretical framework consisting of a hierarchical structure to introduce test automation. Conclusion: The findings of this research showed that the absence of systematic processes is one of the factors that hinder the introduction of test automation. Based on the results of the case studies, FAST can be considered as a satisfactory alternative that lies within the scope of introducing and maintaining test automation in software development. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20process%20improvement" title="software process improvement">software process improvement</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20quality" title=" software quality"> software quality</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20automation" title=" test automation"> test automation</a> </p> <a href="https://publications.waset.org/abstracts/103312/a-framework-for-automating-software-testing-a-practical-approach" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/103312.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">144</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13480</span> Machine Learning Approach for Mutation Testing</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Michael%20Stewart">Michael Stewart</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Mutation testing is a type of software testing proposed in the 1970s where program statements are deliberately changed to introduce simple errors so that test cases can be validated to determine if they can detect the errors. Test cases are executed against the mutant code to determine if one fails, detects the error and ensures the program is correct. One major issue with this type of testing was it became intensive computationally to generate and test all possible mutations for complex programs. This paper used reinforcement learning and parallel processing within the context of mutation testing for the selection of mutation operators and test cases that reduced the computational cost of testing and improved test suite effectiveness. Experiments were conducted using sample programs to determine how well the reinforcement learning-based algorithm performed with one live mutation, multiple live mutations and no live mutations. The experiments, measured by mutation score, were used to update the algorithm and improved accuracy for predictions. The performance was then evaluated on multiple processor computers. With reinforcement learning, the mutation operators utilized were reduced by 50 – 100%. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=automated-testing" title="automated-testing">automated-testing</a>, <a href="https://publications.waset.org/abstracts/search?q=machine%20learning" title=" machine learning"> machine learning</a>, <a href="https://publications.waset.org/abstracts/search?q=mutation%20testing" title=" mutation testing"> mutation testing</a>, <a href="https://publications.waset.org/abstracts/search?q=parallel%20processing" title=" parallel processing"> parallel processing</a>, <a href="https://publications.waset.org/abstracts/search?q=reinforcement%20learning" title=" reinforcement learning"> reinforcement learning</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering" title=" software engineering"> software engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a> </p> <a href="https://publications.waset.org/abstracts/141195/machine-learning-approach-for-mutation-testing" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/141195.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">198</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13479</span> A Review Paper for Detecting Zero-Day Vulnerabilities</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Tshegofatso%20Rambau">Tshegofatso Rambau</a>, <a href="https://publications.waset.org/abstracts/search?q=Tonderai%20Muchenje"> Tonderai Muchenje</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Zero-day attacks (ZDA) are increasing day by day; there are many vulnerabilities in systems and software that date back decades. Companies keep discovering vulnerabilities in their systems and software and work to release patches and updates. A zero-day vulnerability is a software fault that is not widely known and is unknown to the vendor; attackers work very quickly to exploit these vulnerabilities. These are major security threats with a high success rate because businesses lack the essential safeguards to detect and prevent them. This study focuses on the factors and techniques that can help us detect zero-day attacks. There are various methods and techniques for detecting vulnerabilities. Various companies like edges can offer penetration testing and smart vulnerability management solutions. We will undertake literature studies on zero-day attacks and detection methods, as well as modeling approaches and simulations, as part of the study process. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=zero-day%20attacks" title="zero-day attacks">zero-day attacks</a>, <a href="https://publications.waset.org/abstracts/search?q=exploitation" title=" exploitation"> exploitation</a>, <a href="https://publications.waset.org/abstracts/search?q=vulnerabilities" title=" vulnerabilities"> vulnerabilities</a> </p> <a href="https://publications.waset.org/abstracts/154312/a-review-paper-for-detecting-zero-day-vulnerabilities" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/154312.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">102</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13478</span> A Proposal for Systematic Mapping Study of Software Security Testing, Verification and Validation</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Adriano%20Bessa%20Albuquerque">Adriano Bessa Albuquerque</a>, <a href="https://publications.waset.org/abstracts/search?q=Francisco%20Jose%20Barreto%20Nunes"> Francisco Jose Barreto Nunes</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software vulnerabilities are increasing and not only impact services and processes availability as well as information confidentiality, integrity and privacy, but also cause changes that interfere in the development process. Security test could be a solution to reduce vulnerabilities. However, the variety of test techniques with the lack of real case studies of applying tests focusing on software development life cycle compromise its effective use. This paper offers an overview of how a Systematic Mapping Study (MS) about security verification, validation and test (VVT) was performed, besides presenting general results about this study. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20test" title="software test">software test</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20security%20verification%20validation%20and%20test" title=" software security verification validation and test"> software security verification validation and test</a>, <a href="https://publications.waset.org/abstracts/search?q=security%20test%20institutionalization" title=" security test institutionalization"> security test institutionalization</a>, <a href="https://publications.waset.org/abstracts/search?q=systematic%20mapping%20study" title=" systematic mapping study"> systematic mapping study</a> </p> <a href="https://publications.waset.org/abstracts/43751/a-proposal-for-systematic-mapping-study-of-software-security-testing-verification-and-validation" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/43751.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">409</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13477</span> A Novel Approach towards Test Case Prioritization Technique</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Kamna%20Solanki">Kamna Solanki</a>, <a href="https://publications.waset.org/abstracts/search?q=Yudhvir%20Singh"> Yudhvir Singh</a>, <a href="https://publications.waset.org/abstracts/search?q=Sandeep%20Dalal"> Sandeep Dalal</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software testing is a time and cost intensive process. A scrutiny of the code and rigorous testing is required to identify and rectify the putative bugs. The process of bug identification and its consequent correction is continuous in nature and often some of the bugs are removed after the software has been launched in the market. This process of code validation of the altered software during the maintenance phase is termed as Regression testing. Regression testing ubiquitously considers resource constraints; therefore, the deduction of an appropriate set of test cases, from the ensemble of the entire gamut of test cases, is a critical issue for regression test planning. This paper presents a novel method for designing a suitable prioritization process to optimize fault detection rate and performance of regression test on predefined constraints. The proposed method for test case prioritization m-ACO alters the food source selection criteria of natural ants and is basically a modified version of Ant Colony Optimization (ACO). The proposed m-ACO approach has been coded in 'Perl' language and results are validated using three examples by computation of Average Percentage of Faults Detected (APFD) metric. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=regression%20testing" title="regression testing">regression testing</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title=" software testing"> software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20case%20prioritization" title=" test case prioritization"> test case prioritization</a>, <a href="https://publications.waset.org/abstracts/search?q=test%20suite%20optimization" title=" test suite optimization"> test suite optimization</a> </p> <a href="https://publications.waset.org/abstracts/25042/a-novel-approach-towards-test-case-prioritization-technique" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/25042.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">338</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13476</span> Component Based Testing Using Clustering and Support Vector Machine </h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Iqbaldeep%20Kaur">Iqbaldeep Kaur</a>, <a href="https://publications.waset.org/abstracts/search?q=Amarjeet%20Kaur"> Amarjeet Kaur</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software Reusability is important part of software development. So component based software development in case of software testing has gained a lot of practical importance in the field of software engineering from academic researcher and also from software development industry perspective. Finding test cases for efficient reuse of test cases is one of the important problems aimed by researcher. Clustering reduce the search space, reuse test cases by grouping similar entities according to requirements ensuring reduced time complexity as it reduce the search time for retrieval the test cases. In this research paper we proposed approach for re-usability of test cases by unsupervised approach. In unsupervised learning we proposed k-mean and Support Vector Machine. We have designed the algorithm for requirement and test case document clustering according to its tf-idf vector space and the output is set of highly cohesive pattern groups. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title="software testing">software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=reusability" title=" reusability"> reusability</a>, <a href="https://publications.waset.org/abstracts/search?q=clustering" title=" clustering"> clustering</a>, <a href="https://publications.waset.org/abstracts/search?q=k-mean" title=" k-mean"> k-mean</a>, <a href="https://publications.waset.org/abstracts/search?q=SVM" title=" SVM "> SVM </a> </p> <a href="https://publications.waset.org/abstracts/32164/component-based-testing-using-clustering-and-support-vector-machine" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/32164.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">430</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13475</span> Analytical Study of Data Mining Techniques for Software Quality Assurance</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Mariam%20Bibi">Mariam Bibi</a>, <a href="https://publications.waset.org/abstracts/search?q=Rubab%20Mehboob"> Rubab Mehboob</a>, <a href="https://publications.waset.org/abstracts/search?q=Mehreen%20Sirshar"> Mehreen Sirshar</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Satisfying the customer requirements is the ultimate goal of producing or developing any product. The quality of the product is decided on the bases of the level of customer satisfaction. There are different techniques which have been reported during the survey which enhance the quality of the product through software defect prediction and by locating the missing software requirements. Some mining techniques were proposed to assess the individual performance indicators in collaborative environment to reduce errors at individual level. The basic intention is to produce a product with zero or few defects thereby producing a best product quality wise. In the analysis of survey the techniques like Genetic algorithm, artificial neural network, classification and clustering techniques and decision tree are studied. After analysis it has been discovered that these techniques contributed much to the improvement and enhancement of the quality of the product. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=data%20mining" title="data mining">data mining</a>, <a href="https://publications.waset.org/abstracts/search?q=defect%20prediction" title=" defect prediction"> defect prediction</a>, <a href="https://publications.waset.org/abstracts/search?q=missing%20requirements" title=" missing requirements"> missing requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20quality" title=" software quality"> software quality</a> </p> <a href="https://publications.waset.org/abstracts/26206/analytical-study-of-data-mining-techniques-for-software-quality-assurance" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/26206.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">467</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13474</span> Software Cloning and Agile Environment</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ravi%20Kumar">Ravi Kumar</a>, <a href="https://publications.waset.org/abstracts/search?q=Dhrubajit%20Barman"> Dhrubajit Barman</a>, <a href="https://publications.waset.org/abstracts/search?q=Nomi%20Baruah"> Nomi Baruah</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software Cloning has grown an active area in software engineering research community yielding numerous techniques, various tools and other methods for clone detection and removal. The copying, modifying a block of code is identified as cloning as it is the most basic means of software reuse. Agile Software Development is an approach which is currently being used in various software projects, so that it helps to respond the unpredictability of building software through incremental, iterative, work cadences. Software Cloning has been introduced to Agile Environment and many Agile Software Development approaches are using the concept of Software Cloning. This paper discusses the various Agile Software Development approaches. It also discusses the degree to which the Software Cloning concept is being introduced in the Agile Software Development approaches. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=agile%20environment" title="agile environment">agile environment</a>, <a href="https://publications.waset.org/abstracts/search?q=refactoring" title=" refactoring"> refactoring</a>, <a href="https://publications.waset.org/abstracts/search?q=reuse" title=" reuse"> reuse</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20cloning" title=" software cloning"> software cloning</a> </p> <a href="https://publications.waset.org/abstracts/16005/software-cloning-and-agile-environment" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/16005.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">530</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13473</span> Human Immunodeficiency Virus (HIV) Test Predictive Modeling and Identify Determinants of HIV Testing for People with Age above Fourteen Years in Ethiopia Using Data Mining Techniques: EDHS 2011</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=S.%20Abera">S. Abera</a>, <a href="https://publications.waset.org/abstracts/search?q=T.%20Gidey"> T. Gidey</a>, <a href="https://publications.waset.org/abstracts/search?q=W.%20Terefe"> W. Terefe</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Introduction: Testing for HIV is the key entry point to HIV prevention, treatment, and care and support services. Hence, predictive data mining techniques can greatly benefit to analyze and discover new patterns from huge datasets like that of EDHS 2011 data. Objectives: The objective of this study is to build a predictive modeling for HIV testing and identify determinants of HIV testing for adults with age above fourteen years using data mining techniques. Methods: Cross-Industry Standard Process for Data Mining (CRISP-DM) was used to predict the model for HIV testing and explore association rules between HIV testing and the selected attributes among adult Ethiopians. Decision tree, Naïve-Bayes, logistic regression and artificial neural networks of data mining techniques were used to build the predictive models. Results: The target dataset contained 30,625 study participants; of which 16, 515 (53.9%) were women. Nearly two-fifth; 17,719 (58%), have never been tested for HIV while the rest 12,906 (42%) had been tested. Ethiopians with higher wealth index, higher educational level, belonging 20 to 29 years old, having no stigmatizing attitude towards HIV positive person, urban residents, having HIV related knowledge, information about family planning on mass media and knowing a place where to get testing for HIV showed an increased patterns with respect to HIV testing. Conclusion and Recommendation: Public health interventions should consider the identified determinants to promote people to get testing for HIV. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=data%20mining" title="data mining">data mining</a>, <a href="https://publications.waset.org/abstracts/search?q=HIV" title=" HIV"> HIV</a>, <a href="https://publications.waset.org/abstracts/search?q=testing" title=" testing"> testing</a>, <a href="https://publications.waset.org/abstracts/search?q=ethiopia" title=" ethiopia"> ethiopia</a> </p> <a href="https://publications.waset.org/abstracts/34140/human-immunodeficiency-virus-hiv-test-predictive-modeling-and-identify-determinants-of-hiv-testing-for-people-with-age-above-fourteen-years-in-ethiopia-using-data-mining-techniques-edhs-2011" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/34140.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">496</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">13472</span> An Empirical Evaluation of Performance of Machine Learning Techniques on Imbalanced Software Quality Data</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ruchika%20Malhotra">Ruchika Malhotra</a>, <a href="https://publications.waset.org/abstracts/search?q=Megha%20Khanna"> Megha Khanna</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The development of change prediction models can help the software practitioners in planning testing and inspection resources at early phases of software development. However, a major challenge faced during the training process of any classification model is the imbalanced nature of the software quality data. A data with very few minority outcome categories leads to inefficient learning process and a classification model developed from the imbalanced data generally does not predict these minority categories correctly. Thus, for a given dataset, a minority of classes may be change prone whereas a majority of classes may be non-change prone. This study explores various alternatives for adeptly handling the imbalanced software quality data using different sampling methods and effective MetaCost learners. The study also analyzes and justifies the use of different performance metrics while dealing with the imbalanced data. In order to empirically validate different alternatives, the study uses change data from three application packages of open-source Android data set and evaluates the performance of six different machine learning techniques. The results of the study indicate extensive improvement in the performance of the classification models when using resampling method and robust performance measures. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=change%20proneness" title="change proneness">change proneness</a>, <a href="https://publications.waset.org/abstracts/search?q=empirical%20validation" title=" empirical validation"> empirical validation</a>, <a href="https://publications.waset.org/abstracts/search?q=imbalanced%20learning" title=" imbalanced learning"> imbalanced learning</a>, <a href="https://publications.waset.org/abstracts/search?q=machine%20learning%20techniques" title=" machine learning techniques"> machine learning techniques</a>, <a href="https://publications.waset.org/abstracts/search?q=object-oriented%20metrics" title=" object-oriented metrics"> object-oriented metrics</a> </p> <a href="https://publications.waset.org/abstracts/41990/an-empirical-evaluation-of-performance-of-machine-learning-techniques-on-imbalanced-software-quality-data" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/41990.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">418</span> </span> </div> </div> <ul class="pagination"> <li class="page-item disabled"><span class="page-link">&lsaquo;</span></li> <li class="page-item active"><span class="page-link">1</span></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=2">2</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=3">3</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=4">4</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=5">5</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=6">6</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=7">7</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=8">8</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=9">9</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=10">10</a></li> <li class="page-item disabled"><span class="page-link">...</span></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=450">450</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=451">451</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques&page=2" rel="next">&rsaquo;</a></li> </ul> </div> </main> <footer> <div id="infolinks" class="pt-3 pb-2"> <div class="container"> <div style="background-color:#f5f5f5;" class="p-3"> <div class="row"> <div class="col-md-2"> <ul class="list-unstyled"> About <li><a href="https://waset.org/page/support">About Us</a></li> <li><a href="https://waset.org/page/support#legal-information">Legal</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/WASET-16th-foundational-anniversary.pdf">WASET celebrates its 16th foundational anniversary</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Account <li><a href="https://waset.org/profile">My Account</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Explore <li><a href="https://waset.org/disciplines">Disciplines</a></li> <li><a href="https://waset.org/conferences">Conferences</a></li> <li><a href="https://waset.org/conference-programs">Conference Program</a></li> <li><a href="https://waset.org/committees">Committees</a></li> <li><a href="https://publications.waset.org">Publications</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Research <li><a href="https://publications.waset.org/abstracts">Abstracts</a></li> <li><a href="https://publications.waset.org">Periodicals</a></li> <li><a href="https://publications.waset.org/archive">Archive</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Open Science <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Open-Science-Philosophy.pdf">Open Science Philosophy</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Open-Science-Award.pdf">Open Science Award</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Open-Society-Open-Science-and-Open-Innovation.pdf">Open Innovation</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Postdoctoral-Fellowship-Award.pdf">Postdoctoral Fellowship Award</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Scholarly-Research-Review.pdf">Scholarly Research Review</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Support <li><a href="https://waset.org/page/support">Support</a></li> <li><a href="https://waset.org/profile/messages/create">Contact Us</a></li> <li><a href="https://waset.org/profile/messages/create">Report Abuse</a></li> </ul> </div> </div> </div> </div> </div> <div class="container text-center"> <hr style="margin-top:0;margin-bottom:.3rem;"> <a href="https://creativecommons.org/licenses/by/4.0/" target="_blank" class="text-muted small">Creative Commons Attribution 4.0 International License</a> <div id="copy" class="mt-2">© 2024 World Academy of Science, Engineering and Technology</div> </div> </footer> <a href="javascript:" id="return-to-top"><i class="fas fa-arrow-up"></i></a> <div class="modal" id="modal-template"> <div class="modal-dialog"> <div class="modal-content"> <div class="row m-0 mt-1"> <div class="col-md-12"> <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button> </div> </div> <div class="modal-body"></div> </div> </div> </div> <script src="https://cdn.waset.org/static/plugins/jquery-3.3.1.min.js"></script> <script src="https://cdn.waset.org/static/plugins/bootstrap-4.2.1/js/bootstrap.bundle.min.js"></script> <script src="https://cdn.waset.org/static/js/site.js?v=150220211556"></script> <script> jQuery(document).ready(function() { /*jQuery.get("https://publications.waset.org/xhr/user-menu", function (response) { jQuery('#mainNavMenu').append(response); });*/ jQuery.get({ url: "https://publications.waset.org/xhr/user-menu", cache: false }).then(function(response){ jQuery('#mainNavMenu').append(response); }); }); </script> </body> </html>