Amit Tayade Thoughts on QA | SDET

Steps to follow:           1)   Launch the Eclipse IDE and from Help menu, click “ Install New Software ”. 2) You will see a dialog window, click “ Add ” button. 3) Type name as you wish, lets take “ TestNG ” and type “ http://beust.com/eclipse/ ” as location. Click OK. 4) You come back to the previous window but this time you must see TestNG option in the available software list. Just Click TestNG and press “ Next ” button. 5) Click “ I accept the terms of the license agreement ” then click  Finish . 6) You may or may not encounter a Security warning, if in case you do just click  OK . 7) Click  Next  again on the succeeding dialog box until it prompts you to Restart the Eclipse. 8) You are all done now, just Click  Yes . 9) Proceed with your workplace. 10) After restart, verify if TestNG wa...

Finally, this tool will provide good element locators for you quickly, for you to use in your test. Generally, I use this tool first, and then Firepath if this tool can’t find a unique way to identify the element I want. To install:  Open Firefox and search for “webdriver element locator”. The first hit should be for  addons.mozilla.org  again–install the addon into Firefox from there, and it’ll be available to you to use later.

//Using Firefox profile set AcceptUntrustedCertificates to ture  
 FirefoxProfile profile=new FirefoxProfile();  profile.setAcceptUntrustedCertificates(true);  //Then pass that profile while creating Firefox driver  WebDriver Driver = new FirefoxDriver(profile);  

In Agile Methodology, team's capacity can be measured in terms of story points and those points can be determined using estimated time or user story complexity. The first approach i.e. estimation based on time assumes equal expertise in team and does not indicate the difference between the hard to complete story and the one which is very easy and undemanding – this approach considers only how long the work will take to complete. The problem with this approach is a junior member may estimate more for a user story than an expert or senior member, in this case if we map time with story points then velocity may appear higher as compared to other members in team – which is not correct – also this brings in mind that the focus of this approach is more on a individual than the team. Let’s talk about the other approach which is based on user story complexity – it refuses to quantify work in terms of time because this would undermine the self organization central to ...