Intelligent Recognition Method of Web Application Categories Based on Multi-layer Simhash Algorithm

A relevant consequence of the expansion of the web and e-commerce is the growth of the demand of new web sites and web applications. As a result, web sites and applications are usually developed without a formalized process, and web pages are directly coded in an incremental way, where new pages are obtained by duplicating existing ones. Duplicated web pages, having the same structure and just differing for the data they include, can be considered as clones. The identification of clones may reduce the effort devoted to test, maintain and evolve web sites and applications. Moreover, clone detection among different web sites aims to detect cases of possible plagiarism. In this paper we propose an approach. based on similarity metrics, to detect duplicated pages in web sites and applications, implemented with HTML language and ASP technology. The proposed approach has been assessed by analyzing several web sites and Web applications. The obtained results are reported in the paper with respect to some case studies.

An unlimited keyboard support is one of the main accessibility requirements for web pages and web applications. But it is not sufficient that the user can perform all actions on the page using the keyboard. In addition designers of web sites or web applications have to make sure that keyboard users can use their pages with acceptable performance. We present GOMS models for mouse and keyboard navigation in web pages and web applications. These models can be used to compare keyboard navigation with mouse navigation. Such a comparison allows us to decide if the amount of keyboard support for a web page or web application is sufficient or if there is an unacceptable disadvantage for keyboard users.

In recent years, the World Wide Web has become an ideal platform for developing Internet applications. World Wide Web service and application engineering is a complex task. Many web applications at present are large-scale and involve hundreds or thousands of web pages and sophisticated interactions with users and databases. Thus, improving the quality of web applications and reducing development costs are important challenges for the Internet industry. One way to resolve the difficulty is to provide web application developers with an integrated development environment. In this paper, I propose an efficient methodology and development environment for web application programs. This environment includes a design model to represent data and navigational structure, a modeling language for the notation technique of the design model, and a process model to define development stages.

Web Applications (WAs) are complex systems and it is difficult to understand their architecture without proper documentation. Due to high pressure of meeting deadlines and short time to market, WAs are liable to be poorly structured and are rarely well documented. Even if documentation is present, it often does not comply with code because code is updated without updating documentation. This leads to problems during maintenance. To improve understanding of a system, attempts can be made to recover architecture from the source code by analyzing the relations and dependencies between a system's components. Architecture of WAs revolves around its web pages (WPs). In this paper, we present a tool for extracting relations between WPs within WAs. WAFE is capable of extracting a large number of relations, and uses combination of procedural language analysis and object oriented language analysis along with WP identifiers (name terms). Another important feature of WAFE tool is its language independence i.e. one can make it functional for any server side language by writing a few regular expressions.

It is possible to create interactive, responsive web applications that allow user-generated contributions. However, the relevant technologies have to be explicitly deployed by the authors of the web pages. In this work we present the concept of parasitic and symbiotic web applications which can be deployed on arbitrary web pages by means of a proxy-based application platform. Such applications are capable of inserting, editing and deleting the content of web pages. We use an HTTP proxy in order to insert JavaScript code on each web page that is delivered from the web server to the browser. Additionally we use a database server hosting user-generated scripts as well as high-level APIs allowing for implementing customized web applications. Our approach is capable of cooperating with existing web pages by using shared standards (e.g. formatting of the structure on DOM level) and common APIs but also allows for user-generated (parasitic) applications on arbitrary web pages without the need for cooperation by the page owner.

Software testing is indispensable to assure software quality. Traditional software testing techniques are insufficient for modern web applications due to their unique characteristics, such as highly dynamic generation of web pages and interactions with DOM elements. Meanwhile, existing web testing techniques are cumbersome to use in long-term maintenance and evolution because the tests are often brittle in the presence of fast changes to web pages. In this paper, we propose an automatic test generation technique for dynamic web applications. Our technique effectively decouples test code from web pages by automatically generating page objects. Based on page objects, our technique performs iterative feedback directed random test generation. Our evaluation on seven real-world web applications demonstrates that the proposed technique achieves reasonable code coverage (from 23.3% to 90.8%) and can effectively explore dynamically generated web pages (around 14.7 times more than the original static web pages), revealing hundreds of HTML issues and five real errors in the applications.

It is desirable for web applications to be reusable, for example in case a vendor wants to deliver new valuable services by using and combining existing applications quickly. One of the well-known ways of reusing web applications, Mashup, has become popular in the web development community and applied to many open web sites, as we can just combine the data retrieved from Web pages or APIs of the web applications. But in the case of the Mashup of enterprise web applications, or Enterprise Mashup, it is quite difficult since these applications are often not intended to be reusable and have no Web APIs. That means we have to create the Web APIs for the applications, which takes much work. In this paper, we describe a light-weight Web API creation methodology in order to create Web APIs for enterprise web applications much more easily than we can by extending the source code. The created Web API can connect to the web application just as a client who has an account does. So we can create a Web API for Enterprise Mashup without modifying the application at all and we can call the Web API securely using the user account information of the application. We developed the implementation of our methodology and applied it to actual applications to evaluate its effectiveness.

Web application development from simple web pages to complex interactive platforms (including social networks, e-commerce systems, corporate portals) requires new approaches, tools and technologies. JavaScript libraries and frameworks play a special role in developing web applications, simplifying the creation of effective, scalable, and convenient interfaces. The purpose of the article is to research the problems and prospects of using React in combination with Redux when creating web applications with a complex structure, to assess the advantages of their joint use in comparison with similar tools and to develop the web application “FarmerProducts”. The research methodology consists of the main methodological approaches and technological tools for developing web applications. Such methods, in particular, are: system and comparative analysis – to identify the features of creating web applications; method of expert assessments, which involves the study of literary sources and information resources, conducting interviews and surveys of experts, as well as the processes of developing and testing scalable and high-performance web applications based on the use of React and Redux. The scientific novelty of the research is the analysis of modern tools (React, Angular, Vue. js) for developing web applications, identifying problems and prospects for their use, creating an author’s web application (using React and Redux), which includes an intuitive interface, a flexible database, simplifying the process of working with the application by using a stack of modern technologies. Conclusions. The paper analyses the problems and prospects of using modern web application development tools; focuses on React, which is suitable for different projects; conducts a comparative analysis of React with Angular, Vue. js and Svelte, identifies their main characteristics, advantages, disadvantages; demonstrates the dependence of the choice of tools on the project context (React in combination with Redux can provide an optimal balance between performance, flexibility and scalability); describes the author’s web application – the FarmerProducts online store; identifies further ways to improve this web application.

WebWriter: A browser-based editor for constructing Web applications

With conventional regression test tools for Web applications, it is difficult to specify the values to be verified that are repeated output inside loop statements. We need to select each of these values displayed in Web pages with the mouse. This paper presents a method that automates regression testing of Web applications on the server side. This method makes it easy to specify values to be verified and enables us to specify them when we develop Web applications. We can directly check the verification results on the Web pages that are shown in the Web browser. If we find a fault, we can even directly modify a part of the server program in the Web browser that corresponds to the currently displayed Web page.

Automated testing is important for validating the behavior of programs with complex user interfaces, such as web applications. In the enterprise context, web applications are popular client-server programs that provide rendered web pages as a user front-end, and the business logic is typically implemented on the server-side. In this paper, we present an approach to automatically generate test cases for component-based user interfaces for web applications built on the Java EE platform. We generate a sequence of user actions to navigate through the web application. For each supported user action, we gather constraints from the view template describing the web page (e.g. a button must be enabled in order to be clicked by a user), as well as constraints that are introduced while executing a server-side component. We have implemented our approach in a tool to determine its practical use in an experiment.

The keyboard is the most universally supported input method operable by people with disabilities. Yet, many popular websites lack keyboard accessible mechanism, which could cause failures that make the website unusable. In this paper, we present a novel approach for automatically detecting and localizing keyboard accessibility failures in web applications. Our extensive evaluation of our technique on real world web pages showed that our technique was able to detect keyboard failures in web applications with high precision and recall and was able to accurately identify the underlying elements in the web pages that led to the observed problems.

Data analysis is a data inspecting and transforming process for the purpose of making conclusions and obtaining useful information to help make a decision about disclosed forecasts. There are numerous technologies and methods for analyzing data that are mainly determined by the type of data.The paper presents models for organizing web applications' data based on the integrated use of structured data from databases of web applications and unstructured data derived from web pages and server log files. Bu studying the many existing approaches to data analysis from web applications, a summary of the process of data analysis from web applications has been made. An example of using this approach in e-commerce applications is given. The software tools that can be used to perform analyses have been pointed out.

Much work has been done on automating regression testing for Web applications, but most of them focus on test data generation or test execution. Little work has been done on automatically determining if a test passed or failed; testers would need to visually confirm the result which can be a tedious task. The difficulty is compounded by the fact that parts of a Web page (such as advertisements) may change each time the Web application is executed even though it has no bearing on the Web application function itself. We thus propose a test oracle for automatically determining the result of regression testing a Web application. The key point of our approach is the identification of parts that may change, which we call variable region. We first generate the expected result, by executing the original (premodification) Web application multiple times so that variable regions can be identified. Then, after the Web application is modified, regression testing is conducted by comparing the output of the modified Web application against the expected output. An evaluation confirmed the usefulness of our approach. Keywordsweb application testing; regression test; image compar-

We present an approach to write web applications in the programming languages Haskell [8] and Curry [6]. The web applications we propose are directly based on the Hypertext Transfer Protocol (HTTP) – no additional protocol on top of HTTP is necessary. Although the main ideas are not new and already applied using other programming languages, we believe that features present in modern declarative languages – especially algebraic datatypes – serve well to represent resources on the web. 1 TRANSFER OF RESOURCE REPRESENTATIONS A resource is any piece of information named by a Uniform Resource Identifier (URI). A web application provides access to internally stored information over the Internet or accesses such information provided by other web applications. Usually, (a representation of) this information is transferred using the Hypertext Transfer Protocol (HTTP) [3] – possibly employing some protocol on top of it. Note that we do not primarily consider applications running inside a web browser like [4, 7, 9]. HTTP provides different methods to access resources from which the most important are the GET and the POST method. GET is used to retrieve some information, e.g., web browsers use GET to ask for the content of web pages. POST is used to send information to be processed by a server, e.g., entries in a web form can be sent to the server using POST. While processing the request, the server can update its internally stored information and usually sends back a result of this process. Web applications differ in their use of these two HTTP methods: RPC-style web applications are accessible through a single URI and communication is performed using the POST method. A representation of a procedure call is transferred to the server, which returns a representation of the result of this call as answer to the POST request. Note that both retrieval and update operations are performed using the POST method in RPC-style web applications and the interface of such applications is determined by the procedure calls that are understood by the server. Fielding [2] proposes another architectural style for web applications: He proposes to use the POST method only to update the internal state of the server and to use the GET method to purely retrieve information. Consequently, everything that should be available for retrieval by clients needs to be identified by an own URI. This is a big difference to RPC-style web applications that are usually accessible ?This work was partially supported by the German Research Council (DFG) grant Ha 2457/5-1. through a single URI. In the architectural style proposed by Fielding, a client sends an HTTP GET request to an URI to retrieve a representation of the resource identified by this URI corresponding to the current state of the server. To change this state, the client sends a POST request to the URI of the resource he wants to update. Fielding calls this architectural style Representational State Transfer (REST). The interface of a RESTful web application is given by the methods of HTTP and the URIs identifying the applications resources. In this work, we show how the interface given by the most important HTTP methods can be made available to Haskell or Curry programmers, hiding the details of HTTP communication.