network profile
| bio | website | lazeryattack.com |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years |
| seen | May 18 at 13:34 | |
| stats | profile views | 10 |
|
May 26 |
awarded | Editor |
|
May 26 |
revised |
What are good guidelines to determine when to automate a test? added 1 characters in body |
|
May 26 |
answered | What are good guidelines to determine when to automate a test? |
|
May 23 |
comment |
How is Selenium different from other GUI automation tools? This will be my last comment on this then. I'm not saying I haven't come across people using the wrong terminology before, it happens lots. I do however belive that it should be corrected when it happens so that people are taught the correct terminology and in general expectations are set appropriatly. If somebody tells me they want me to write unit tests i'll explain what unit tests are, explain why I won't be writing them and tell them what I will be writing and what the tests I write will deliver. Continuing to use incorrect terminology when you know it's wrong just compounds the issue. |
|
May 23 |
comment |
How is Selenium different from other GUI automation tools? Please don't try and make out that testers call acceptance tests unit tests. This is just plain wrong terminology and continuing to use it will just confuse anybody new to the industry. |
|
May 23 |
comment |
How is Selenium different from other GUI automation tools? To quote the definition "unit testing is a method by which individual units of source code are tested to determine if they are fit for use" You are invariably not testing an individual unit of source code if you are testing a GUI (multiple units of code will be used to generate the page displayed). You could possibl classify it as an integration test (checking that all the units of code work when integrated together in a page) but that is strething the definition a bit IMHO. |
|
May 22 |
comment |
How is Selenium different from other GUI automation tools? You can't make unit tests with Selenium, if you are testing the GUI you are not testing a unit of code, acceptance tests and integration tests or even end to end tests yes but definetly not unit tests. Unit tests are the developers domain, not the testers. |
|
May 21 |
comment |
How is Selenium different from other GUI automation tools? I don't personally bother with grid, I find it easier to just get Hudson to kick of tests on various machine. Anyway the point I was making is that Selenium is a lot more than a one trick "record and play" pony which is what you original answer implied. I agree that record and play can be a good place to start, but it really is just a small part of Selenium. |
|
May 20 |
comment |
How is Selenium different from other GUI automation tools? The recording part of Selenium is a very small part. Experienced user of selenium don't go near IDE they write everything from scratch in code. Record and play is probably the least useful part of selenium if you are looking at creating robust and reliable regression tests on a dynamic website. |
|
May 18 |
awarded | Supporter |
|
May 18 |
comment |
What are the challenges around the integration of Manual and Automated Tests? Pretty much says everything I would have said :) Another problem I have dealt with before is the idea that automated scripts can be offshored and manual testing can be performed onshore. This generally doesn't work, the offshore team doesn't know what you are testing and you will spend more time supporting them, telling them how to make the automated tests do what you want and reviewing scripts than if you had written the automated tests yourself. There needs to be buy in for automation for it to work, it's not a case of hire some junior devs offshore and all will be good because it won't. |
|
May 18 |
comment |
Which locator do you use with Selenium CSS or XPath? @Jason I would suggest that you were using poorly constructed XPath's then, a well formed Selenium XPath will ne no more brittle than a CSS locator. |
|
May 18 |
comment |
A way to match on text using CSS locators :contains() is not part of the current CSS3 specification so it will not work on all browsers, only ones that implemented it before it was pulled. (see w3.org/TR/css3-selectors) |
