Tag Info

Hot answers tagged

18

I work as a Manual tester on a big project. My project follows Agile methodology. I test a Web-based application. I sometimes ask my self , that am i giving any value to the stakeholders? So, the value that you are giving to stakeholders is the reduction in the amount of defects that go to production. The cost of fixing a defect drastically increases ...


14

Writing unit tests is not difficult - as the saying goes, it is matter of simple programming :-) So if you are competent programmer, and are willing to learn necessary skills and patterns, you can do it as QA engineer. But IMHO (and best practices say that) developers are much better suited to write unit test - because unit tests use internal calls to ...


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


8

One very helpful trait would be ability ("knack") to search available information and being able to find what you need. If you did simple search in QA (I used search string "how to start qa") you would find many answers, like: How to become a good QA employee How can I transition into getting into QA? What does a Sofware QA Person Need to Know to Perform ...


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

As for tutorials on SoapUI, sadly the majority of them are sub-par at best and out of date. If you want to learn SoapUI the best option is likely to jump in feet first and hit the ground running. My background is primarily API testing, with a specialty with SoapUI and Groovy, so I will try and give some hints and pointers to get you started. SoapUI's core ...


6

The one thing I think it's necessary to know: The essence of the job is to provide decision makers with accurate, relevant, timely information about the system, to help them make better decisions. Of course, you will also need to learn zillions of strategies and techniques for providing that information. But the key is to remember the point of what you do: ...


6

A few thoughts based on my not-quite-ten years experience as a tester and automator: Learn the principles, not a tool - If you understand the principles of automation and how it works, you're going to be in a much better strategic position than if you simply learn an automation tool. You could do worse than to dig through Joe Strazzere's blog and Alan ...


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


5

What do you think? Should you eat one meal at a time and 2 to 3 meals a day? Or should you eat sufficient meals for 30 days at once and enjoy the remaining 29 days? Keep things as simple as possible! Combining everything and testing it all at once may make things too complicated to handle...


5

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


5

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


5

A perspective from a developer: A unit test is best written in conjunction with the code it's testing. It will shape the code to some extent: the need to write a test forces the code to be easily testable, which limits some code smells/anti-patterns. For example, a method that directly calls the database to obtain a user name will be hard to unit test until ...


4

Install Google chrome. Install Blazemeter extension in chrome. Download JMeter and set it up. Lots of tutorials available for that. Record scripts with blazemeter and download them. Run the scripts in JMeter. Tada...


4

Try this line of code: Driver.findElement(By.xpath("enter your xpath")).click(); Hope it works out!


4

Tester is just a label on an employee. Testing provides value. It is virtually impossible to write bug-free software, and so software that has not been tested is virtually guaranteed to be buggy. Someone needs to test it. Who tests depends on the circumstances. Some people are good at testing, and some are not. You probably want the person who tests to ...


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

Although i do not have much idea about it but i think you can give selenium grid a try. I read on seleniumhq.org that with selenium grid you can create a master slave architecture, where one master machine will control several slaves to send request to a common server. Maybe this can help solve your issue!


4

Great question. I see two issues, as follows. Using random data may lead to unrepeatable results. You can mitigate this by logging (or otherwise recording) every random choice you make, and then playing those choices back. That could be as easy as recording the initial seed to your random number generator, assuming your data does not change over time. ...


4

Depends on the tech powering your game. Unity has such testing tools (link).


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


3

I would like to answer we are too serious for jokes but... http://extremesoftwaretesting.com/Humor/JokesSoftwareTesting.html


3

You can open 2 browsers by initializing 2 firefox instance and then get() method will open URL in each browser accordingly. Do you want to use 1 firefox instance i.e. open it, close it and open it again ?


3

Yes, you can run headless with either Headless Chromium or with PhantomJS .. Keep in mind that running with Selenium Grid or SauceLabs is equally as good as running headless.


3

I am in no way trying to be rude, but I think the hiring team may be setting themselves up for failure. Having worked on many many automation projects and worked with many people of varying skill levels, it is actually just about impossible for someone with no automation background to jump in to automation and get it right the first time. With no guidance ...


3

Most automated testing frameworks require the user to either write in scripting language or in an actual programming language. Thus test automation equals writing code to run tests against the application. Maybe some frameworks work fully with recording the tests, but experience learns that recorded tests are harder to maintain. As an automated test ...


3

Test Automation is an extremely broad subject. It doesn't just mean performing regression testing or load testing with a specific tool, although that's often what employers want (it's easy to identify). The ability to create specific programmatic solutions to help you test is hugely valuable. Over the years automation tool vendors have tried to make the ...


3

By definition testing EVERYTHING will take INFINITE TIME. Which I bet is less than optimal (unless your boss is OK with that - then you just found safe job for life :-) So you need to agree with your boss about some metrics to limit and prioritize "everything". Make a survey among your customers which OTHER applications they use, on which platforms. Or ...



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