Skip to main content

What are Challenges faced using selenium Automation Testing

By

What are Challenges faced using selenium Automation Testing ?

Challenges faced using selenium Automation Testing
·        Dealing with pop-up windows
·        Testing dynamic text or content
·        How to go about testing Flash
·        Capturing screen shots, either to file or in some form of report
·        Iteration of the test case, running it repeatedly with some minor change
·        Data Driven Testing, using suites of pre-cooked data or generating it on the fly
·        Generating useful test status reports
·        Setting up Remote Control
·        Setting up Grid
·        handling Alerts Popups
·        Switching between windows
·        Working with frames.
·        Field validation
·        How to identify dynamic objects.
·        Xpath and CSS locators for identifying elements.
·        File Upload/Download Using : Java-AutoIT-Selenium
·        Handling Multiple Popup Windows.
·        Switching with multiple Windows
Example :
·        Need to Describes how did faced that problem and how did you overcome that problem with example as below.
   

  •      In Selenium, you identify a UI element with a locator.  There are many kinds of locators, e.g.IDs, names, and XPaths.  If you have never used XPath, you should expect to invest some time familiarizing yourself with it.  On Firefox, Firebug and Firepath are invaluable for inspecting the DOM and figuring out locators.
  •           On common problem with UI automation is dealing with timing issues, e.g. you press a button and it takes an indeterminate amount of time for the web page to refresh.  You can try hard-coding delays into your test or you can tell Selenium to wait for a element in the page to appear.  I recommend the latter.   I don't remember what the API is for that, but I imagine someone here can speak up about that.  
  •           Another recurring problem I've had, and which shows up repeatedly on the Selenium forums, has to do with tabbing between fields.  Selenium has APIs for filling in a text field and clicking a button, but it doesn't have an explicit "hit the Tab button while you're in this text field" API. The Selenium forums suggest various workarounds.  I think the appropriate workaround depends on the situation.  In my application, something special happens when the focus leaves a password field.  Under the covers, the app detects the focus leaving the field via a blur event.  I haven't figured out what action to tell Selenium to perform to cause a blur event to happen, but there is a "fireEvent" method on the Selenium interface that explicitly causes an event to fire.  

Few More :

  •  If something is changed without the knowledge of the Automation Tester like headings of the page or title of the page, the script will Fail.
  •   Even if the content team changed the text on the webpage which you might have captured it in your script for some reason the regression suite will fail. 

  •  If for any reason the servers are down and you running your test suit overnight, the test might Fail. If you don't have a dev or test environment, the automation script might cause loads on the Live server( In case you hitting one server ) which makes the server to collapse and this will effect the business. 


 If the requirements are constantly changing and the site is very dynamic, its very hard to automate.

Comments

Post a Comment

Popular posts from this blog

Testing Types

By
         Installation testing Main article: Installation testing An installation test assures that the system is installed correctly and working at actual customer's hardware. Compatibility testing Main article: Compatibility testing A common cause of software failure (real or perceived) is a lack of its compatibility with other application software, operating systems (or operating system versions, old or new), or target environments that differ greatly from the original (such as a terminal or GUI application intended to be run on the desktop now being required to become a web application, which must render in a web browser). For example, in the case of a lack of backward compatibility, this can occur because the programmers develop and test software only on the latest version of the target environment, which not all users may be running. This results in the unintended cons...
Post a Comment
Read more

What really happens when you navigate to a URL

By
As a software developer, you certainly have a high-level picture of how web apps work and what kinds of technologies are involved: the browser, HTTP, HTML, web server, request handlers, and so on. In this article, we will take a deeper look at the sequence of events that take place when you visit a URL. 1. You enter a URL into the browser It all starts here: 2. The browser looks up the IP address for the domain name   The first step in the navigation is to figure out the IP address for the visited domain. The DNS lookup proceeds as follows: Browser cache –  The browser caches DNS records for some time. Interestingly, the OS does not tell the browser the time-to-live for each DNS record, and so the browser caches them for a fixed duration (varies between browsers, 2 – 30 minutes). OS cache  – If the browser cache does not contain the desired record, the browser makes a system call (gethostbyname in Windows). The OS has its own cache....
Post a Comment
Read more

Software Testing Basics - Software Testing Interview Questions and Answers

By
1. Can you explain the PDCA cycle and where testing fits in? Software testing is an important part of the software development process. In normal software development there are four important steps, also referred to, in short, as the PDCA (Plan, Do, Check, Act) cycle. Let's review the four steps in detail. Plan:  Define the goal and the plan for achieving that goal. Do/Execute:  Depending on the plan strategy decided during the plan stage we do execution accordingly in this phase. Check:  Check/Test to ensure that we are moving according to plan and are getting the desired results. Act:  During the check cycle, if any issues are there, then we take appropriate action accordingly and revise our plan again. So developers and other stakeholders of the project do the "planning and building," while testers do the check part of the cycle. Therefore, software testing is done in check part of the PDCA cyle. 2. What is the difference between white box,...
Post a Comment
Read more