Hot answers tagged

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 ...


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 ...


6

There are two (actually both are very similar) techniques in order to reveal the tests which tend to be "false/positive" ones – Error Seeding and Mutation Testing. The both principles are based on introducing the errors in the application's program code, mainly in the places where it will have the most dramatical effect for application. It can be for ...


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

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 ...


4

Recording tests often leads to hard to maintain tests, therefore most experienced testers prefer hand coding automated tests over recording. Automated tests often cover the same area multiple times, in order to setup data, or for example navigation. When a central part of the application changes this could result in multiple tests failing, all these tests ...


4

Try to use driver.findElements instead. It returns a list of all WebElements. All means also the not visible elements. Here some code to iterate thru the list and only do something with the displayed items. List<WebElement> elements = driver.findElements(By.className("vfmThumbnail")); java.util.Iterator<WebElement> i = elements.iterator(); ...


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

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 ...


4

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.


4

You'll have to discuss this with your team and company, among other things it depends on the internal culture, skills, schedules and even internal politics. FWIW I've seen both successful and miserable results from the following: A test team owning entire automation, from the infrastructure to test cases and execution Separate infrastructure team, ...


4

You don't specify whether the developers are already writing tests at lower levels than the UI, e.g. unit/component/API level tests. It's also not clear how closely the developers and testers work together currently. I'd agree with Rsf that it depends very much on internal culture, skills etc, which only you and your team can decide. But here are some ...


4

Selenium is an industry standard for web GUI. But desktop GUI automation is almost an untilled field. There are several disparate tools that are able to deal with few types of GUI. I know only one cross-platform open source project for GUI testing based on accessibility technologies (therefore text-based): it's LDTP. But in my mind the interface is really ...


4

Agile practises are all about automated testing, therefor on the long run I think manual testers should be worried for their jobs. Currently I am talking with recruiters and they ask me why are there not more people with your skill set, that of an automated tester. Since there is a lot of demand for this in the Netherlands at the moment. If you take a look ...


4

Is it only GUI testing? No, it's up to you. Personally, I create automation tests for the test cases that are often executed, and the test that is simple (not complex). Do we also have to create Integration automation scripts? Yes, we do. It is part of testing and hence the testers' job. What would be our boundaries when a developer also does their own ...


4

In my opinion you should not mix positive and negative paths because every test has to be independent and give a clear result. Suppose that you create 100 scripts both positive and negative and all tests with negative paths fail, in theory you'll never know if they would fail even with positive ones until you fix your code. My suggestion is having a ...


4

I use the page object pattern myself. It addresses two main things: Defines the finder in one place Names the finder with english-like words Good things. However this doesn't address the issue of how to combine series of steps that are then used in multiple places. To do this you can use use functions / procedures / methods in the language you are ...


4

Like Michael said the Page object pattern makes the finder easier to use. I try to maintain a pattern of having a test only verifying one thing or possibly one screen. In your example I would assume in your first test, you would be testing everything about the post being visible. In your 2nd test, the create a post step is only a setup step so that you have ...


4

Project Management Institute is one of the most well-known. More at https://www.pmi.org/certification/agile-management-acp.aspx Another leader is: https://www.scrumalliance.org/certifications which breaks out various roles including developer A personal note is that in my experience this certifications will make you entry-level and only a year or two in ...



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