Amit Tayade Thoughts on QA | SDET

Locating elements in web applications created by  Ext JS  framework could be a total nightmare for UI automators, as Ext JS generates one of the most complex DOM structures which have dynamic IDs with a large amount of duplicate class names. Unlike automating applications with simple DOM structures, Selenium WebDriver's built-in methods like  By.Id ,  By.ClassName ,  By.Name  would barely identify anything in Ext JS applications. In most of the cases,  By.CssSelector  or  By.XPath  will be neccessary, even though using them are not that straightforward either. Hopefully this article would help developers write the most concise meaningful and human readable locators, so that maintenance cost can be kept minimum when automating ExtJS applications. Ext JS Example DON'Ts Don't match only IDs Don't use highly position-dependent XPaths Don't match single class name only Don't perform exact match on multiple classes Don't use tools to generate locato

Thoughts on QA : Hybrid and Native Apps ? :

Thoughts on QA : Appium execution on real devices USB /WiFi :

Thoughts on QA : How to Setup a Hub,Node and parallel execution for... : How to Setup a Hub and Node for Selenium Grid Selenium Grid allows us to execute our tests in multiple machines (physical / virtual) and...

How to Setup a Hub and Node for Selenium Grid Selenium Grid allows us to execute our tests in multiple machines (physical / virtual) and multiple browsers with different versions, which dramatically speeds up test execution and helps in reducing total amount of time required for test execution. For example , if we have a script that takes 100 minutes to execute sequentially , we could break that down to 10 short tests script run across 10 machines, and can complete them in 10 minutes without copying your test code to the other machine. A grid consists of a single hub, and one or more nodes, Hub and Node are the two main elements that you come across when using grid. Download selenium grid and selenium server. Hub   the Hub is the central point which will receive all the test requests along with information on which browser, platform (i.e. WINDOWS, LINUX, etc) and where the test should be run. Based on the request received, it will distribute them to the registered nodes.

1       Execution on real devices using USB - Assume all the below Prerequisites are installed and configured :- 1. JDK should be installed 2. Android should be installed and path should be setup in your machine 3. Appium should be installed. 4. Configure Device with Developer Mode option enabled In order to   run Appium test cases on real devices, we need to connect real android device to PC by enabling USB debugging mode.To test on a real device or on on a simulator, we need SDK to be installed on your machine. Appium will take the advantage of the SDK to connect to the real device connected via USB or simulator. First Enable Developer Option, To enable Developer Option in android device, Click on Settings and find out ‘About Phone’ option. Follow below steps – Step 1   : Click on About Phone option Step 2   : Click on Version Information Step 3   : Now you will find an option called ‘Build Number’. Step 4   : Keep clicking Build number option for seven