-
Chris McMahon is a software tester and former professional bass player. His background in software testing is both deep and wide, having tested systems from mainframes to Web apps, from the deepest telecom layers and life-critical software to the frothiest eye candy. Chris has been part of the greater public software testing community since about 2004, both writing about the industry and contributing to open source projects like Watir, Selenium, and FreeBSD. His recent work has been to start the process of prying software development from the cold, dead hands of manufacturing and engineering into the warm light of artistic performance. A dedicated Agile telecommuter on distributed teams, Chris lives deep in the remote Four Corners area of the U.S. Luckily, he has email: christopher.mcmahon@gmail.com.
-
Do you have a question for our experts?
Contributions from Chris McMahon
- Automation testing: Seven tips for test design
- Wikis for Agile ALM collaboration
- Agile software development: Issue tracking solutions
- Estimation approaches in Agile development
- Pair development: Pairing programmers and testers with
- Test automation: Three approaches to browser testing
- STAREAST: Testing with FitNesse and Selenium
- Agile development: Lessons for small projects
- The value of visible requirements
- Designing automated tests for the user interface
- Automated and exploratory UI testing
- Managing large Agile application lifecycle projects
- Software iteration deployment: retrospectives
- DevOps: Fostering collaboration in software development
- 100% Distributed Agile teams: Communication and workflo
- The software experience report: Record what you learn
- Breaking the bug reporting rules
- The perfect storm: Multiple mishaps lead to disaster
- Automating software development: The Big Red Button
- Self-organizing teams exposed