This article by Adam Goucher identifies a handful of heuristics that apply to software testing automation. While not an exhaustive set, it is a useful one, and it will put you on the path to identifying and collecting your own set of automation heuristics. Heuristics are used in testing as rules of thumb or prompts for solving a particular problem or class of problems.
This video explains why we need to develop page components for our tests in order to create smaller and more dynamic page components. Web pages are no more the monolithic static pages of the past. They contain a lot of small elements that we interact with, so being able to focus on the components is a better solution to automate the testing of web applications.
At the Google Test Automation Conference 2011 , the opening keynote was presented by Alberto Savoia, Director of Engineering and Innovation Agitator at Google. He believes that software testing as we knew it is dead – or at least moribund – in which case we should stick a fork in it and proactively take it out of its misery for good.
Load testing is almost always conducted to address one or more risks related to expense, opportunity costs, continuity, and/or corporate reputation. In two blog posts, Tarun Arora discusses the topic. In part 1, he explains why Performance Testing the application is important, presents the test tools available in Visual Studio Ultimate 2010 and various test rig topologies. In part 2, he analyzes the details of web performance and load tests as well as why it’s important to follow a goal based pattern while performance testing your application.
The unit testing feature is part of the support within the Oracle SQL Developer family of products. This article presents the SQL Developer unit testing framework for testing PL/SQL objects, such as functions and procedures, and monitoring the results of such objects over time. You create tests, and for each you provide information about what is to be tested and what result is expected. The SQL Developer implementation of unit testing is modeled on the classic and well known xUnit collection of unit test frameworks.
Test-driven development (TDD) is a programmer practice that’s been employed by a growing number of software development teams for the past dozen years. Does TDD impact you personally? If you’re a manager, what should you expect from teams using TDD? How do you know if they’re doing a good job? Is there any advantage of TDD over sporadic after-the-fact unit testing?
in this blog post, Lisa Crispin proposes a short explanation on how to use and interpret the Agile Testing Quadrants defined by Brian Marick. The quadrants are a taxonomy that can help teams to plan their testing and to make sure they have all the resources they need to accomplish it.