Usage of Selenium Tool for Regression Testing

Size: px

Start display at page:

Download "Usage of Selenium Tool for Regression Testing"

Melanie McDaniel
6 years ago
Views:

1 Usage of Selenium Tool for Regression Testing 1 K.Aarati, 2 K.Swetha Sastry 1,2 Department of Computer Science, Malla Reddy Engineering College for Women Maisammaguda, Hyderabad Abstract Web applications are used in the following fields like business, communication, education and entertainment. Whatever may be the application testing is very important to indicate working condition of that product. Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not. Testing is executing a system in order to identify any errors, or missing requirements.this paper basically deals with regression testing using a tool Selenium. I.INTRODUCTION Testing can be defined as a process of analyzing a software product to detect the enhancements between existing and required conditions (that is defects/errors/bugs) and to evaluate the features of the software product. Testing and Debugging: Testing : It involves identifying bug/error/defect in a software without correcting it. Normally professionals with a quality assurance background are involved in bugs identification. Testing is performed in the testing phase. the setup is handed over to the testing team to formally execute the test cases. Unit testing is performed by the respective developers on the individual units of source code assigned areas. The developers use test data that is different from the test data of the quality assurance team. The goal of unit testing is to isolate each part of the program and show that individual parts are correct in terms of requirements and functionality. Integration Testing: Integration testing is defined as the testing of combined parts of an application to determine if they function correctly. Integration testing can be done in two ways: Bottom-up integration testing and Top-down integration testing. System Testing: System testing tests the system as a whole. Once all the components are integrated, the application as a whole is tested rigorously to see that it meets the specified Quality Standards. This type of testing is performed by a specialized testing team. System testing enables us to test, verify, and validate both the business requirements as well as the application architecture. Debugging : It involves identifying, isolating, and fixing the problems/bugs. Developers who code the software conduct debugging upon encountering an error in the code. Debugging is a part of White Box Testing or Unit Testing. Debugging can be performed in the development phase while conducting Unit Testing or in phases while fixing the reported bugs. Quality of a software application include Quality model External metrics Internal metrics Quality in use metrics Quality attributes for any software are: Functionality Reliability Usability Efficiency Maintainability Portability What testing shows: Errors Requirements conformance Performance An indication of quality Different Levels of Testing[1]: Unit Testing: System testing is important because of the following reasons: System testing is the first step in the Software Development Life Cycle, where the application is tested as a whole. The application is tested thoroughly to verify that it meets the functional and technical specifications. The application is tested in an environment that is very close to the production environment where the application will be deployed. Validation Testing: Validation testing follows integration testing. Focuses on user visible actions and user-recognizable output from the system. Designed to ensure that This type of testing is performed by developers before 45

All functional requirements are satisfied All behavioral characteristics are achieved All performance requirements are attained Documentation is correct Usability and other requirements are met (e.g.

2 All functional requirements are satisfied All behavioral characteristics are achieved All performance requirements are attained Documentation is correct Usability and other requirements are met (e.g., transportability, compatibility, error recovery, maintainability) When to Start Testing? An early start to testing reduces the cost and time to rework and produce error-free software that is delivered to the client. However in Software Development Life Cycle (SDLC), testing can be started from the Requirements Gathering phase and continued till the deployment of the software. It also depends on the development model that is being used. For example, in the Waterfall model, formal testing is conducted in the testing phase; but in the incremental model, testing is performed at the end of every increment/iteration and the whole application is tested at the end. Testing is done in different forms at every phase of SDLC: During the requirement gathering phase, the analysis and verification of requirements are also considered as testing. Reviewing the design in the design phase with the intent to improve the design is also considered as testing. Testing performed by a developer on completion of the code. When to Stop Testing? Verification and Validation are important things to be done to assess quality of a software product. II ABOUT SELENIUM AND REGRESSION TESTING Selenium is an open source tool[8] for automating the testing. It focuses on automating web applications. It can be operated on different browsers and operating systems. It supports Mobile Devices. It has four components. Selenium Integrated Development Environment (IDE) Selenium Remote Control (RC) WebDriver Selenium Grid Selenium Integrated Development Environment (IDE): Is a Firefox plugin which allows testers to record their actions as they follow the workflow that they need to test. Selenium Remote Control (RC): It supports langauages such as Java, C#, PHP, Python, Ruby and PERL to create more complex tests. Selenium WebDriver: Is the extension of Selenium RC which sends commands directly to the browser and retrieves results. Selenium Grid: Used to run parallel tests across different machines and different browsers simultaneously which results in minimized execution time. ARCHITECTURE OF SELENIUM It is difficult to determine when to stop testing, as testing is a never-ending process and no one can claim that a software is 100% tested. The following aspects are to be considered for stopping the testing process: Testing Deadlines Completion of test case execution Completion of functional and code coverage to a certain point Bug rate falls below a certain level and no highpriority bugs are identified Automation for web applications: Automation means running repeatable tests against the application to be tested using a software tool. Automation supports Management decision Frequent regression testing Verification & Validation: 46

Finding defects which are not solved by manual testing Giving frequent feedback to developers We Perform Several Selenium-Based Tests: Dynamic Tests - We verify dynamic elements of web applications.

3 Finding defects which are not solved by manual testing Giving frequent feedback to developers We Perform Several Selenium-Based Tests: Dynamic Tests - We verify dynamic elements of web applications. Functional Tests - We verify form-based inputs, checkboxes, radio buttons, drop-down lists, submit and cancel operations, or any other browser-supported input. Link Tests - We verify broken links and missing pages. Static Tests - We verify static elements of web applications Regression Testing: Whenever a change in a software application is made, it is quite possible that other areas within the application have been affected by this change. Regression testing is performed to verify that a fixed bug hasn't resulted in another functionality or business rule violation. The intent of regression testing is to ensure that a change, such as a bug fix should not result in another fault being uncovered in the application. With selenium we can develop Regression test scripts and suits in the selected and supported languages which are long term maintainable. MODULAR FRAMEWORK: Objectives Low Maintenance Robustness <classes> <class name="com.module1.screen1"/> Test Coverage <class name="com. Module1.Screen2"/> Scalability <class name="com. Module2.Screen1"/> Usability <class name="com. Module2.Screen2"/> Modular Approach: </classes> </test> Screen1=GUI Component1+Business Component1 Flow1=Screen1+Screen2 TC1=Flow1+Flow2 The main folders in Modular framework would be Lib: This folder contains the default jar files, which supports selenium and other tools Src: This folder contains screen components or flows and generic methods, which in turn used in test cases. Screen1.Java Screen is a composition of GUI Component, generic components and Business components TestCases: This folder contains xml files corresponding to each test case. In below example testcase is a composition of screens or flows Example: TC1.XML <test name="btmresearch-smoketests" junit="false" preserve-order="true"> Debug: This folder contains ant xml file corresponding to each user, so that team members can work collaboratively without manipulating the driver code. Release: It contains xml files to execute batch tests. Still 47

4 we need to do more R&D on this component. Properties File: It contains global variables, which can be accessible throughout the project. Reporting: Custom excel reporting to be developed using Java code. By Analysing[7][9]the example for regression testing is taken There is a chance of addition of dispensable items then that test case is to be tested. Addition of drugs can occur. For example we have different pharmacies like A,B, and C. The insurance company is tied with A&B, now C also wanted to add in this network. Then all the input of A&B are taken and it is given as input to C. Using Selenium we will test all previous modules and we will test only new testcase manually. III CONCLUSION Web applications will continuously change so there is an requirement to automate the system so that we can increase performance of the software product[7].for this we can use regression testing to automate. Using Selenium tool testing is very easy. The automation solution included the creation of a new abstraction layer on top of Selenium that allows the team to create and execute tests with a simpler and easy to maintain language. The Example considered here is processing Health Insurance policy claims. The requirements include here are facilitating change management and control, speeding up the creation, updating of test scenarios/scripts as well as, bringing scalability to and reducing costs of maintenance of the test operations. The cases to be considered are Member eligibility Member Validation Disposable Items validation Non-Disposable items Validation Drug Validation Dosage Regression testing for health insurance is performed by the quality assurance team within the organisation after the development team has completed their work. It is common that developing and upgrading software within any type of hardware can fix various faults. However developing any code can create new faults and reemergence of old ones could be costly in the long run. Therefore it is good practice within any quality assurance process, to utilise a third party independent device that would provide reporting tools on the device under test to determine if any faults are present. When a patient is admitted in hospital,the hospital will take insurance data from the person.there are several modules in this.insurance company Z will check all the data given by X hospital.company Z will check prescribed drugs,all dispensable items and non dispensible items and then concludes what are things that are to be covered by insurance and what not.hospital X sends persons data also.then z will send this data to company Y to verify whether that person is valid or not and what can be covered in Insurance. Then that data is verified and tested by company Y.He will generate report to insurance company Z.Then Z will send all the details to the person who got admitted.the company Y tests test cases using regression testing. Software testing plays crucial role in developing a software product. we can use so many testing techniques for testing the software. The tester needs to be very patient, creative & open minded. They have to act according to End User perspective. We can achieve good results by using automated testing so that we can reduce time in generating testcases. so to test we use selenium for regression testing because it is very easy and lot of time can be saved. We can test n no. of cases very easily Whenever there is a change request or Enhancement in the product we can perform testing very easily. REFERENCES [1]. Gaurav Saini, Kestina Rai Software Testing Techniques for Test Cases Generation International Journal of Advanced. Research in Computer Science and Software Engineering Volume 3, Issue 9, September 2013 [2]. Daniel J. Mosley Bruce A. Posey, Just enough software test automation [3]. Somerville, Software Engineering [4]. Isabella and Emi Retna, study paper on test case generation for GUI based testing International Journal of Software Engineering & Applications (IJSEA), Vol.3, No.1, January [5]. Graham, D. Fewster, M. (2012), " Experiences of Test Automation: Case Studies of Software Test Automation", (1st ed.).addison- WesleyProfessional. [6]. Dustin, E. Rashka, J. Paul, J. (2008) "Automated Software Testing: Introduction, Management, and Performance". Addison-Wesley Professional. [7]. Itti Hooda, Rajender Chhillar Study of Test Case Generation Techniques,International Journal of Computer Applications ( ) Volume 107 No. 16, December [8]. Introduction-Selenium Documentation.Available at: ducing-selenium. Access in: 48

5 October, 24th [9]. Drake, T.(1996), Measuring Software quality: A case study. IEEE Computer, 29(11), [10]. Karambir, Kuldeep Kaur Survey of Software Test Case Generation Techniques, International Journal of Advanced Research incomputer Science and Software Engineering, Volume 3, Issue 6, June [11]. Rajib Mall, Fundamentals of software engineering, The prentice hall of India, 3rd Edition, [12]. Pressman, Software Engineering: A Practioner sguide 5/e. 49

Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not.

i About the Tutorial Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not. Testing is executing a system in order