The company I work for develops several different products as part of a unified offering. These products need to work with each other and with products from other companies. Each product development team has its own manual QA and automation team, and we have a solutions testing team that ensures interoperability between our products and […]
One of the automation engineers on our team is extremely thorough. When she does code reviews, she sends back lengthy emails, and she provides a lot of good information regarding coding practices. Her devotion to detail is a real asset to the team. However, she is getting burned out on code reviews and sometimes I […]
During my recent job hunt, test automation came up in practically every interview, typically some broad question like, ‘So, how would you go about implementing test automation?” My standard answer is that you generally get the best bang for your buck the farther deeper in your code you test. As an example, I contrast maintenance […]
Over at the Google Testing Blog, MiÅ¡ko Hevery has a short post on what constitutes small, medium and large testing. To summarize his post: Small: make sure each class works properly in isolation Medium: make sure the classes work together Large: end-to-end scenario testing to make sure that everything is wired together properly
Over at his I. M. Testy blog, BJ Rollison offers succinct definitions of five approaches to automated testing: record and playback automation, keyword or action-word driven automation, scripted automation, procedural automation, and model based automation. It’s a good quick reference.
Today, Elisabeth Hendrickson has a blog post out titled How Much to Automate? Agile Changes the Equation. In this post, she points out the value of timely, reliable automated test results: But teams that do practice TDD and ATDD wind up with large suites of automated tests as a side effect. (Yes, itâ€™s a side […]
I had a conversation recently with a colleague whose small company had contracted out their testing. One of the (several) problems of this arrangement, he said, was that the testers had created automated UI tests, but they were having trouble keeping the tests up to date. The colleague asked me what I thought they should […]
John Overbaugh offers some advice for finding the right testing tool. In addition to listing factors to consider in evaluating tools, John also offers some tips on how to elicit advice from others. Good stuff.
Recently, I’ve had several conversations at work about the cost/benefit analysis of performing automated GUI testing (in our case, using Borland SilkTest, of course) in our agile environment. In general, automated GUI testing is most useful in the following situations: when the UI of the application under test (AUT) does not change much, and when […]