InfoQ Homepage Automation Content on InfoQ
-
Book Review: Experiences of Test Automation
“Experiences of Test Automation” is a compilation of experiences in the field that is hard to read from end to end but serves well as a reference for experienced readers by providing examples of approaches, obstacles and solutions in a variety of domains and technologies as well as insightful overviews from the authors.
-
Thoughts on Test Automation in Agile
Rajneesh Namta shares the lessons he’s learned while automating software tests on a recent Agile project. The techniques he recommends illustrate how the Agile principles we follow when building software apply equally as well to building an automated regression test suite: start small, build iteratively and incrementally, prioritize, focus on value, work transparently, respond quickly to change.
-
Interview and Book Review: Specification by Example
Gojko Adzic has written the book Specification by Example, explaining the set of techniques for describing the functional and behavioural aspects of a computer system in a way that they are useful to the development team (expressed ideally as executable tests), understandable by non-technical stakeholders and maintainable to remain relevant despite changing customer demands.
-
Test automation and Continuous Delivery
This article shows how automating certain programmable aspects of a test suite can help software delivery. Covered are automated testing, costs per deployment, tests as documentation & manual testing.
-
Skills for Scrum Agile Teams
The skills required to be hyper-productive in agile projects are different from those required by a traditional one. This article identifies behavioral and technical skills required for a team to have that edge. Anyone who acquires these "delta" traits should be equipped with the right set of behavioral and technical skills, which enable them to work effectively in an agile project.
-
A Tester's Learning Journey
The software industry is changing fast. More and more teams put testing up front and center; they use tests to drive development. In this article, Lisa Crispin talks about how her attitude and curiosity have shaped her career and kept her passion for testing software fresh.
-
5 Configuration Management Best Practices
There has been a lot of conversation going on around the configuration of applications, and how to manage it. This article explores things people can do from within their code to make their lives, and the lives of anyone else who has to administer or maintain their application, easier. These patterns have been used a number of times on ThoughtWorks projects, and they have proven their worth.
-
Overcoming Technical Challenges for Adopting Agile Methods in the Enterprise
This article touches upon challenges to adopting agile methods within the enterprise and provided strategies for addressing them. Set up development environments in a consistent fashion using automated scripts and checklists, facilitate automated testing and continuous integration by using standard tooling and test data transparency, and ensure a stricter criteria for the done definition.
-
Improving the Performance of Automatic Configuration Management Processes by Encouraging Human Intervention
In this case study, the pattern of automatic processes interlaced with human intervention provided bwin with an instrument to raise process efficiency in CM drastically. Furthermore, successes of the incorporation of human factors into change management was an increased visibility and appreciation of the context and importance of change amongst team members and stakeholders across the company.
-
Excerpts from an Interview with James Bach
Following are the most relevant excerpts from the interview with James Bach at Oredev 2008. He covers topics like: engineering, why we should be telling success stories, opening our minds to other scientific domains, automated testing and exploratory testing.
-
Layered Architecture for Test Automation
In test automation, code involved in testing is not only test logic, but also a bunch of other supporting code, like URL concatenation, XML parsing, UI, etc. Test logic can be buried in this unrelated code, which has nothing to do with test logic itself, making test code hard to read and maintain. In this article, the layered architecture of test automation is presented to solve this problem.
-
Scalability Worst Practices
In this article, former Orbitz lead architect Brian Zimmer discusses scalability worst pratices. Topics covered include The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.