Hot answers tagged

33

We cannot automate CAPTCHA, as it is not meant to be automatized. How to deal with CAPTCHA? Either ask dev team for a workaround, like configure CAPTCHA in test environment in such a way it will always accept 1 specific value. Ask developer to disable the CAPTCHA module in testing environment. If your are using custom CAPTCHA module, you can ask developer ...


25

You don't, that is the whole idea behind a good CAPTCHA. CAPTCHA stands for: Completely Automated Public Turing test to tell Computers and Humans Apart So, by definition, resolving a CAPTCHA cannot be automated: Otherwise it could not tell computers and humans apart and hence fails being a CAPTCHA. Howto handle a CAPTCHA in a test environment: If ...


11

Automated tests are tests that can be run automated, often developed in a programming language. In this case we talk about the individual test cases, either unit-tests, integration/service or end-2-end tests. Test automation is a broader concept and includes automated tests. From my perspective it should be about the full automation of test cycles from ...


10

I don't know whether a certification is necessary for automation testing, but you definitely require good coding skills and logic development skills for it. Its advantageous to learn Java as its open source and hence there are countless forums and communities to seek kelp. Plus many of the automation testing tools (specially open source testing tools) use ...


9

The best way to help your career is to learn how to test and become very good at it. James Bach has a really good post directed at new testers, that is worth reading (lots of recommendations) and he says this about certifications: Don’t get certified. There are no respectable commercial testing certifications. If you are forced to get certified for ...


9

Well, the important thing in the question is to be sure you understand the world beyond your nose. Of course you're not directly impacted by the SDLC, but still, 80% of the shop around you will be. In other words, the recruiter asks the question to ensure you are able to get out of your role, and see things as a whole. That's important for your career to be ...


9

No. The items you mention scale very differently and there are far too many factors and resources that will get used. For instance if I time requests on a local server using an application I'll find things like 1 user = 10 second response average (time per request) 10 users = 2.5 second average 100 users = 2.5 second average 1000 users = 20 second average ...


9

Does this actually catch, before production, many of the "surprise" problems we might anticipate? Or is there a more fundamental flaw in the approach that will cause deleterious changes to pass testing and affect production? You are wise to have a test system that you can use for catching performance issues, but your "scaling" approach is flawed. ...


8

Testing is not a standalone activity because: resolving bugs means talking with product and development to make sure that the bugs are well understood and that the path to correct them makes sense for all. understanding business requirements and what an application is trying to achieve means working with business users and product owners understanding ...


7

List cheeses = driver.findElements(By.className("cheese")); findElements() does not wait, but returns list of elements (located by locator). List is empty if nothing is found. http://docs.seleniumhq.org/docs/03_webdriver.jsp Also, Selenium elders very strongly advise to use only explicit waits (no implicit). And especially warn about mixing implicit and ...


7

WaitForPageLoad() continue's after all the data for the page has been retrieved and I think when the browser OnLoad() function is called. Its possible the browser is still executing JavaScript or processing CSS. Meaning your elements might not be visible on the page just yet. Instead of waiting for the page to load you should use an explicit wait to wait ...


7

When working with agile (or any methodology) I would suggest making your testers part of the team, rather having a separate QA team which is isolated from all the work. (This also means sitting the testers with the developers if you are in the same office.) In your points above you have listed a lot of tasks, these tasks are not the sole responsibility of ...


7

From this and from your other question about using Excel as input for Selenium, I have a feeling that you need to improve your general programming skills. If you are competent programmer, selenium is just yet another library you have to use to make your program to do what you want it to do. Not trivial, but not rocket science either (for a competent ...


6

The short version: Don't sweat on automation or test cases. Chances are you won't get time to build it because there's too much that has to be manually tested now. Instead focus on building light-weight, easy to maintain documentation of the key elements of the software you're testing. The longer version: This is my world. I'm the sole tester in a team of ...


6

There are two sides of this question: Your result is not 100% because there is an issue with the Automation test designed by you. If this is the problem, then definitely you need to improve your automated test cases, so that they execute perfectly (not in terms of approach) but in terms of requirement and coverage. Once they are corrected your ...


6

Of-course you should a try to answer all questions in a job interview and if you don't know you can answer that you don't know, much better then making up bullshit. It might be good to openly question how this question relates to the job offering if you think its outside of the scope of the actual job. In this case with SDLC I would expect all team members ...


5

Although, this question is too broad to answer but in short I can say 'It depends upon number of factor which tool you want to use'. Project/Organization budget Scope of Automation Skillset available with team Complexity/functionalities of automation Reporting Test case management Tool support, etc. Don't just compare the tools theoretically, use them ...


5

I think the test-case is the what and the test-script is the how of the test. Its possible to defined high level test-cases to describe what needs to be tested. The test-scripts contain all the detail to really execute the test.


5

First priority should be for everyone to trust the test suite again, failing tests suites will not give this feeling. Disable all the broken tests and run all the tests a hundred times to also get rid of all the flickering tests (that work sometimes, but not always). Start running the tests on each commit or at-least daily to make sure the tests can be ...


5

On our Group we have both a combination of applications that are UI driven and others that are just public facing API Interfaces. In both cases the development team is usually doing unit testing and a single a happy path integration test. The QA Team (of which I am part of) we generate automated test scripts that are repeatable and verify all of the business ...


5

You can prove your skills as programmer/developer without writing automated tests. Learn tools used for other testing-related tasks: load testing, etc. Become expert system administrator. Tools like Jenkins. Logstash to analyze logs (to be more productive as manual tester). Prove your skills by writing scripts needed to manage the test data, like ...


5

What to test and how You definitely need to test full flows of the system, to see whether services understand each other, in particular, when one of service responds with error messages. This is a place where I usually find problems. Mocks will definitely help here. Also, if you're working with queues, then many there might asynchronous events and ...


5

Presumably the database is just a piece of your overall system, and your goal is to determine whether database changes break things or slow the system down. Using a downsized database is a reasonable way to check whether database changes break things. I'm not sure it makes sense to use a downsized database for load testing. Whether this makes sense ...


5

I stumbled upon some black box techniques, but I don't really get how it works. I found sources saying that black box techniques are techniques in which you input something in a program and check if the output matches with the wanted result, if it doesn't, there's an error somewhere. Let's help with the terminology first: Black Box Testing typically ...


5

Sikuli can extract text with OCR (optical character recognition) as described on this page: http://doc.sikuli.org/region.html#Region.text Extracting Text from a Region class Region text() Extract the text contained in the region using OCR. Returns: the text as a string. Multiple lines of text are separated by intervening ‘n’. Note: Since this ...


5

What is Guerrilla Testing : it is a way to get some quick user feedback on your product or prototype. I can say its usability testing. Guerrilla Testing Covers : it covers an activity by which you need to conduct it where your audience are novice users and observe these - Can they find the content? Is the language relevant to them? Have they understood ...


4

Here's how I'd approach this situation (the tl;dr version): Analyze your options and give an indication of the risks involved. Your risk analysis should show your preferred option as having the lowest risk (expressed as a relative number, e.g. 1 being the highest risk and 25 the lowest) and state a few of the biggest risk factors for each potential ...


4

Yes, use soft assertions org.testng.asserts.SoftAssert. Soft assertions are assertions that do not terminate the test when they fail but results are included in the test execution report. More articles on that topic: http://stackoverflow.com/questions/19091526/how-soft-assertions-work ...


4

It all depends what high level operations you have on your page. The requirement of High level functionalities differ from application to application and page to page. Some of the pages may not be having any or some of the options mentioned by you but some may have additional operations like Edit : Change the record to edit mode Delete : Delete the ...


4

The software testing life cycle includes more steps than just the practical "doing". In short it starts with reviewing the design / requirements, going over to planing and designing your tests, execute the tests (often called testing) and finishes with reports. So I think you connect the word "testing" only with the "doing" while having an application ...



Only top voted, non community-wiki answers of a minimum length are eligible