Figure 25 - uploaded by Zuhaimy Ismail
Content may be subject to copyright.
Source publication
![Figure 2: Typical Web Application Structure [2]](profile/Zuhaimy-Ismail/publication/224366357/figure/fig1/AS:284372084248576@1444810996244/Typical-Web-Application-Structure-2_Q320.jpg)
![Figure 3: Sample ReWeb Output[13]](profile/Zuhaimy-Ismail/publication/224366357/figure/fig2/AS:284372084248578@1444810996262/Sample-ReWeb-Output13_Q320.jpg)
A web application is an application that can be accessed via a web browser over a network. Web applications contain client side code and server side code. Web applications undergo changes in the maintenance phase, and retesting changed programs is done thereafter. To retest a program after changes, we can select a subset of the whole test suite on...
Context in source publication
Context 1
... simple user interface was created using Java swing with the help of tutorials in [33] . Figure 24 shows the user interface for running the tool. UploadSessions needs the session file as an input. If no file was entered into the input box (arrow 1) an error message would appear for the user (figure 25) . Run all will run the components in the following order: uploadSessions, JSpider, Constructor and finally the ...
Similar publications
The standard geographic web services WMS (web map service) and WFS (web feature service) comprise respectively two methods GetFeature and GetFeatureInfo that allow to obtain attributes associated to a geographic object represented on a map. Most certainly, the returned result brings semantics to the object but requires adaptation to the theme chose...
Citations
... • Regression testing (Tarhini et al., 2008): This testing focuses on selecting a subset of the test case used to test a web application to cover the changes made to this application. When we modify a web application by adding or removing a certain functionality, software tester must determine the parts of the application that were affected by the modifications to test only these parts and not the whole application. ...
... The aim of a paper can be test automation, test coverage, or assessing a specific quality attribute, such as security. Kuk and Kim (2008), Marchetto et al. (2008), Marchetto and Tonella (2009), Song and Miao (2009), Ran et al. (2009), Andrews et al. (2010, Song et al. (2011), Tkachuk and Rajan (2011), Törsel (2011), Chen et al. (2012, Tanida et al. (2013), Bansal and Sabharwal (2013), Törsel (2013), Arora and Sinha (2013), Törsel (2013), Suhag and Bhatia (2014), Nabuco and Paiva (2014), Polpong and Kansomkeat (2015), Zhang and Tanno (2015), Dixit et al. (2015), Habibi and Mirian-Hosseinabadi (2015), Sengupta and Dasgupta (2015), Qi et al. (2017), Boukhris et al. (2017) and Gao et al. (2022) DFM or data flow graph, DDM or data dependency graph, CFM or CDM or graph Tarhini et al. (2008), Ran et al. (2009) Corazza et al. (2021) and Gao et al. (2022) Markov chain workload model Habibi and Mirian-Hosseinabadi (2015) and Ahmad et al. (2018) ESG, EFG or event functional graph Krüger and Linschulte (2012) and Habibi and Mirian-Hosseinabadi (2015) VFG Liu and Tan (2008) Failure mitigation model Boukhris et al. (2017) and Andrews et al. (2019) Use case description Zhang and Tanno (2015) PITM Liu et al. (2010) SD Suhag and Bhatia (2014) Analysis model that represents the web pages and their relationships Kuk and Kim (2008) In Table 4, the models and graphs used for web applications model-based testing are arranged in descending order from the most commonly used models to the models used the least. One research paper may use more than one model for testing web applications; accordingly, this paper will appear in different sections in Table 4. ...
... Case study Marchetto et al. (2008), Mallouli et al. (2008), Tarhini et al. (2008), Liu and Tan (2008), Marchetto and Tonella (2009), Song and Miao (2009), Ran et al. (2009), Li et al. (2010aLi et al. ( , 2010b, Andrews et al. (2010), Huang et al. (2011), Song et al. (2011), Krüger and Linschulte (2012), Avancini and Ceccato (2012), Törsel (2013), Bansal and Sabharwal (2013), Tanida et al. (2013), Sabharwal et al. (2013), Kao et al. (2013), Aruna and Prasad (2014), Offutt et al. (2014), Suhag and Bhatia (2014), Habibi and Mirian-Hosseinabadi (2015), Polpong and Kansomkeat (2015), Sengupta and Dasgupta (2015), Zhang and Tanno (2015), Stocco et al. (2016) Some studies used more than one evaluation method such as building a tool and then using this tool in many experiments or case studies. Also, for the purpose of evaluation, some studies used an experimental web application while other studies used real world industrial web applications. ...
Due to the importance of web application testing techniques for detecting faults and assessing quality attributes, many research papers were published in this field. For this reason, it became essential to analyse, classify and summarise the research in the field. To achieve this goal, this research conducted a systematic mapping study on 98 research papers in the field of web applications testing published between 2008 and 2021. The results showed that the most commonly used web applications testing techniques in literature are model-based testing and security testing. Besides, the most commonly used models in model-based testing are finite-state machines. The most targeted vulnerability in security testing is SQL injection. Test automation is the most targeted testing goal in both model-based and security testing. For other web applications testing techniques, the main goals of testing were test automation, test coverage, and assessing security quality attributes.
... Over the years, many studies and publications have been reported in literature on the topic of regression testing [2], [3] and [4]. In the following, only some of the approaches discussed in the aforementioned papers in regression testing domain were surveyed. ...
... Over the years, many studies and publications have been reported in literature on the topic of regression testing [2], [3] and [4]. In the following, only some of the approaches discussed in the aforementioned papers in regression testing domain were surveyed. ...
Regression testing is a type of testing that is performed to validate that new changes pushed to the system does not have any adverse effect to the existing features. Automated regression testing greatly reduces the time spent by testers to perform these repetitive and mundane tests and allows them to work on more critical tests. The first problem addressed in this project is to add two automated regression scripts to increase test coverage of the existing test automation framework. The second problem is to optimise the automated regression test run to reduce the test run times. Additionally, to improve the automated test run times, redundant expressions were removed and handled in the outermost loop of the automated test run. The project resulted in the addition of two automated test scripts for the automated test run and a significant test run time reduction of at least 60%.
... Tarhini et al. [23] have proposed a safe regression testing selection technique for web applications based on an Event Dependency Graphs (EDG). The EDG is used to model the certified and the modified web applications. ...
... The affected nodes are used to select test suite for the certified web application. Empirical results show that the technique reduced the test set size [23]. About 44-90% of test cases were eliminated. ...
Regression testing is expensive but an essential activity in software maintenance. Regression testing validates modified software and ensure that the modified parts of the program do not introduce unexpected errors. This paper briefly describes an overview of regression testing specifically regression test selection techniques. Most regression test selection techniques are based on program slicing techniques.
... Details of user's activities in the Graphical User Interface GUI are extracted based on reading Model signals document object (DOM) specific to the browser. Authors in [18] suggested a regression testing approach based on internal information in order to form Time Labeled Transition Systems (TLTS) and Task Precedence Graphs (TPG) for each selected service. The idea was initially proposed in [53] and then extended in [18]. ...
... Authors in [18] suggested a regression testing approach based on internal information in order to form Time Labeled Transition Systems (TLTS) and Task Precedence Graphs (TPG) for each selected service. The idea was initially proposed in [53] and then extended in [18]. Sensitive information was left unprotected which implies that the technique suffers from security issue. ...
... Experiment results show that, the regression testing method is fairly feasible and cost-effective in practice. Tarhini et al. [18] considered a real help desk Web application to evaluate a regression safe testing selection technique. The application is implemented using .Net 2005 environment. ...
... For each affected node goes to the test suit T and check if the node is present in the test cases. It the node is present in the test cases add the test case to the new test suit T' [44]. ...
Service-Oriented Architecture (SOA) removed the gap between software and business. Today, there is a business transformation among enterprises and they adopt a service based information technology (IT) model. So, testing is necessary for SOA based applications. This paper investigates different type of approaches and techniques that address the testing problems of SOA based services. Here we also investigate the differences between SOA and web services and traditional testing and SOA testing. Various testing levels are also discussed in detail. This paper also expresses various testing perspectives, challenges of SOA testing and review the many testing approaches and identify the problems that improve the testability of SOA based services.
... One way of ensuring that such modifications (e.g., bug fixes, patches) have not introduced new faults in the modified system is through systematic regression testing. While regression testing of classical web applications has been difficult[25], dynamism and non-determinism pose an even greater challenge[22]for Web 2.0 applications. In this paper, we propose an automated technique for JAVASCRIPT regression testing, which is based on dynamic analysis to infer invariant assertions. ...
... testing of web applications has received relatively limited attention from the research community[26,25]. Alshahwan and Harman[1]discuss an algorithm for regression testing of web applications that is based on session data[24,8]repair. ...
Web 2.0 applications rely heavily on JavaScript and client-side runtime manipulation of the DOM tree. One way to provide assurance about the correctness of such highly evolving and dynamic applications is through regression testing. However, JavaScript is loosely typed, dynamic, and notoriously challenging to analyze and test. We propose an automated technique for JavaScript regression testing, which is based on on-the-fly JavaScript source code instrumentation and dynamic analysis to infer invariant assertions. These obtained assertions are injected back into the JavaScript code to uncover regression faults in subsequent revisions of the web application under test. Our approach is implemented in a tool called Jsart. We present our case study conducted on nine open source web applications to evaluate the proposed approach. The results show that our approach is able to effectively generate stable assertions and detect JavaScript regression faults with a high degree of accuracy and minimal performance overhead.
... This is a constituent principle of SOA, which we maintain in the approach proposed in this paper. To the best of our knowledge, few proposals are available for regression testing of web services, and most of them exploit the availability of additional documentation or constraints, such as a Control Flow Graph as in [29], or a UML model as in [28]; more sophisticated approaches include a two-level Timed Labeled Transition Systems model with timing constraints (in [33]), or an Event Dependency Graph combining dependencies with interacting components (in [34]). Hou et al. [16] proposed specific quotas to constrain the number of requests, which could help service orchestrators understand the service behavior and test case coverage information; finally, Mei et al. [22] developed a multilevel coverage model to capture business processes based on XPath and WSDL. ...
The attractive feature of Service Oriented Architecture (SOA) is that pieces of software conceived and developed by independent organizations can be dynamically composed to provide richer functionality. The same reasons that enable flexible compositions, however, also prevent the application of some traditional testing approaches, making SOA validation challenging and costly. Web services usually expose just an interface, enough to invoke them and develop some general (black-box) tests, but insufficient for a tester to develop an adequate understanding of the integration quality between the application and the independent web services. To address this lack we propose an approach that makes web services more transparent to testers through the addition of an intermediary service that provides coverage information. The approach, named Service Oriented Coverage Testing (SOCT), provides testers with feedback about how much a service is exercised by their tests without revealing the service internals. In SOCT, testing feedback is offered itself as a service, thus preserving SOA founding principles of loose coupling and implementation neutrality. In this paper we motivate and define the SOCT approach, and implement an instance of it. We also perform a study to asses SOCT feasibility and provide a preliminary evaluation of its viability and value.
... For web applications, oracle comparators [17] typically analyze the differences between server response pages [15]. For highly dynamic web applications, this comparisonbased approach suffers from a high probability of false positives, i.e., differences between old and new pages that are irrelevant and do not point to an actual (regression) fault [15], [18]. For AJAX applications, the run-time dynamic manipulation of the DOM-tree as well as the asynchronous client/server interactions make it particularly hard to control the level of dynamism during regression testing. ...
... While regression testing has been successfully applied in many software domains [9], [14], web applications have gained very limited attention from the research community [19], [18]. Alshahwan and Harman [1] discuss an algorithm for regression testing based on session data [16], [5] repair. ...
There is a growing trend to move desktop applications towards the web using advances made in web technologies such as Ajax. One common way to provide assurance about the correctness of such complex and evolving systems is through regression testing. Regression testing classical web applications has already been a notoriously daunting task because of the dynamism in web interfaces. Ajax applications pose an even greater challenge since the test case fragility degree is higher due to extensive run-time manipulation of the DOM tree and asynchronous client/server interactions. In this paper, we propose a technique, in which we automatically generate test cases and apply pipelined oracle comparators along with generated DOM templates, to deal with dynamic non-deterministic behavior in Ajax user interfaces. Our approach, implemented in Crawljax, is open source and provides a set of generic oracle comparators, template generators, and visualizations of test failure output. We describe two case studies evaluating the effectiveness, scalability, and required manual effort of the approach.
... Regression testing encompasses the selective re-testing of a system to verify that modifications have not caused unintended effects and that the system still complies with its specified requirements [19]. Regression testing of web applications [37] in general and Ajax-based applications in particular is far from trivial due to the high degree of dynamism in such applications. This dynamism is usually caused by various factors such as input data from different users, server-side state, order of event sequences, etc. ...
There is a growing trend to move desktop applications towards the web. This move is made possible through advances in web technologies collectively known as Asynchronous JavaScript and XML (ajax). With ajax, the classical model of browsing a series of pages is replaced by a JavaScript engine (running in the browser) taking control of user interaction, exchanging information updates with the web server instead of requesting the complete next page. The benefits of this move include no installation costs, automated upgrading for all users, increased interactivity, reduced user-perceived latency, and universal access, to name a few. ajax, however, comes at a price: the asynchronous, stateful nature and the use of Javascript make ajax applications particularly error-prone, causing serious dependability threats. In this paper, we evaluate to what extent automated testing can be used to address these ajax dependability problems. Based on an analysis of the current challenges in testing ajax, we formulate directions for future research.
