Test Cases For Web Applications Research Articles

Morpheus Web Testing: A Tool for Generating Test Cases for Widget Based Web Applications

Context: Widgets are reusable User Interfaces (UIs) components frequently delivered in Web applications.In the web application, widgets implement different interaction scenarios, such as buttons, menus, and text input.Problem: Tests are performed manually, so the cost associated with preparing and executing test cases is high.Objective: Automate the process of generating functional test cases for web applications, using intermediate artifacts of the web development process that structure widgets in the web application. The goal of this process is to ensure the quality of the software, reduce overall software lifecycle time and the costs associated with tests.Method:We elaborated a test generation strategy and implemented this strategy in a tool, Morpheus Web Testing. Morpheus Web Testing extracts widget information from Java Server Faces artifacts to generate test cases for JSF web applications. We conducted a case study for comparing Morpheus Web Testing with a state of the art tool (CrawlJax).Results: The results indicate evidence that the approach Morpheus Web Testing managed to reach greater code coverage compared to a CrawlJax.Conclusion: The achieved coverage values represent evidence that the results obtained from the proposed approach contribute to the process of automated test software engineering in the industry.

Optimization Method of Web Fuzzy Test Cases Based on Genetic Algorithm

In order to solve the problems of low code coverage, few vulnerabilities found, and poor fuzzing effect caused by the small number of test cases and single types in Web fuzzing, on the basis of studying the current Web fuzzing methods, the existing fuzzing Web applications are tested Program research. A genetic algorithm-based method for optimizing fuzzing test cases for Web applications is proposed. It analyzes and counts the traffic of public network website business with Web service attack characteristics, and uses genetic algorithms to generate a large number of test cases with various types to explore the Web service vulnerability that exists. Based on the creation of a Web attack signature database with weights, this method uses genetic algorithms to randomly pre-generate the test cases of the fuzzing test, and uses the response of the Web service to repeatedly iterate the weights of different attack signatures in the Web attack signature database. So as to generate the best test cases. Experimental analysis shows that this method effectively finds security vulnerabilities in Web applications.

Integrated Pairwise Testing based Genetic Algorithm for Test Optimization

Generation of Test cases in software testing is an important and a complex activity as it deals with diversified range of inputs. Fundamentally, test case generation is considered to be a multi-objective problem as it aims to cover many targets. Deriving test cases for the Web Applications has become critical to the most of the enterprises. In this paper, a solution for generating test cases for web applications is proposed; the solution uses the System Graph (consisting of links and data dependencies) considering that test cases were based on a combination of input values and data dependencies. Pairwise testing is used to derive the test cases to be executing from entire test cases and then a genetic algorithm is proposed to generate test cases specific to functional testing. The proposed approach was tested through two distinct experiments by measuring the code coverage at every generation and results show that genetic algorithm used increased the fitness value and code coverage. Overall, the results of the paper validate the proposed approach and algorithm, having potential in further construct an automated integrated solution for generating test cases for the entire process.

Investigating the applicability of generating test cases for web applications based on traditional graph coverage

Web applications provide services to hundreds of millions of people throughout the world. However, developers face a range of problems and challenges in testing them, including the fact that web applications run on diverse and heterogeneous platforms and are written using diverse programming languages. Moreover, they can be dynamic, with their contents and structures determined by inputs from users, so they need to be tested to ensure their validity. In this paper, we investigate the ability to generate a set of test cases for web applications based on traditional graph coverage criteria. First, we extracted the in-link and out-link from given web applications in order to draw a web graph, before extracting the prime paths from the graph. After that, the invalid transitions were built from the prime paths. Finally, all the invalid transitions were extended with valid transitions. We evaluated our investigation process by using different sizes of web applications. Two cases studies were used in this paper, the first a small size application and the second a medium size. The results show how difficult it is to run a huge number of test cases generated manually using graph coverage criteria, even for a small web application.

Investigating the applicability of generating test cases for web applications based on traditional graph coverage

Web applications provide services to hundreds of millions of people throughout the world. However, developers face a range of problems and challenges in testing them, including the fact that web applications run on diverse and heterogeneous platforms and are written using diverse programming languages. Moreover, they can be dynamic, with their contents and structures determined by inputs from users, so they need to be tested to ensure their validity. In this paper, we investigate the ability to generate a set of test cases for web applications based on traditional graph coverage criteria. First, we extracted the in-link and out-link from given web applications in order to draw a web graph, before extracting the prime paths from the graph. After that, the invalid transitions were built from the prime paths. Finally, all the invalid transitions were extended with valid transitions. We evaluated our investigation process by using different sizes of web applications. Two cases studies were used in this paper, the first a small size application and the second a medium size. The results show how difficult it is to run a huge number of test cases generated manually using graph coverage criteria, even for a small web application.

Configuring effective navigation models and abstract test cases for web applications by analysing user behaviour

SUMMARYAs web applications become more complex and are used more pervasively, testing demands are increasing without corresponding automated support. One promising approach to automatic test generation is statistical model‐based testing, where logged user behaviour is used to build a usage‐based model of web application navigation, from which abstract test cases are generated. Executable test cases are then created by adding parameter values to the abstract test cases. Several researchers have proposed variations of this approach; however, no one has empirically examined the tradeoffs and implications of the different ways to represent user behaviour in a navigation model and the characteristics of the test cases automatically generated from different models. This paper reports on our exploratory study of automatically generated abstract test cases and the underlying usage‐based navigation models constructed from over 19,000 user sessions across five publicly deployed web applications. Our results suggest how web testers can easily configure statistical model‐based automatic test case generators for web applications toward generating tests closely related to user behaviour or toward new navigations without using large additional test resources. Copyright © 2013 John Wiley & Sons, Ltd.

New test case prioritization strategies for regression testing of web applications

A test case prioritization technique reschedules test cases for regression testing in an order to achieve specific goals like early fault detection. Currently, black box testing of web applications requires manual prioritization of test cases which is very time consuming. We propose a new two level prioritization approach to prioritize test cases for web applications as a whole. Our approach selects modified functionalities in a web application and automatically executes test cases on the basis of the impact of modified functionalities. We suggest several new prioritization strategies for web applications and examine whether these prioritization strategies improve the rate of fault detection for web applications. We propose a new test suite prioritization model for web applications that detects modified functionalities, selects test cases related to those functionalities and reschedules them to detect faults early in test suite execution.

From formal requirements to automated web testing and prototyping

Use cases and user interface prototypes are agile techniques used to specify required functionalities of an object-oriented system. Testing can find most errors of the software and ensure that the requirement specifications are satisfied by the application. We can derive test cases from use cases and run them in user interfaces, but we do it in a mechanical way. In this paper, we propose a new approach for automating the generation of user interface prototypes and test cases for web applications. Starting from a formalization of the requirements based on controlled use cases extended with the system glossary and the user interface specifications, we automatically generate web pages and test cases which are passed as parameters for an automated web testing tool.

Leveraging user-session data to support Web application testing

Web applications are vital components of the global information infrastructure, and it is important to ensure their dependability. Many techniques and tools for validating Web applications have been created, but few of these have addressed the need to test Web application functionality and none have attempted to leverage data gathered in the operation of Web applications to assist with testing. In this paper, we present several techniques for using user session data gathered as users operate Web applications to help test those applications from a functional standpoint. We report results of an experiment comparing these new techniques to existing white-box techniques for creating test cases for Web applications, assessing both the adequacy of the generated test cases and their ability to detect faults on a point-of-sale Web application. Our results show that user session data can be used to produce test suites more effective overall than those produced by the white-box techniques considered; however, the faults detected by the two classes of techniques differ, suggesting that the techniques are complementary.