Peter Walen
Member for
11 years 9 monthsPete Walen has been in some form of software development for over 25 years. He has been a developer, a business analyst, a project manager and now a tester and testing specialist.
Pete describes himself as a Quality Advocate, ScrumMaster, and Product Improver. He has worked in a variety of shops using a variety of development methodologies and has adopted an attitude of “do what makes sense.”
Pete is a member of the American Society for Quality (ASQ), the Scrum Alliance and the Agile Alliance.
All Articles by Peter Walen
All Stories by Peter Walen
| Automation Software Is Production Software When it comes to testing, there tends to be a differentiation between “production software” and everything else. But our ideas and principles about testing software are true for all software, not merely the code that will run in front of customers or the APIs that make things happen. Any software built for a purpose needs to be tested against that purpose, including the software running our test automation. |
|
|
Automation Software Is Production Software When it comes to testing, there tends to be a differentiation between “production software” and everything else. But our ideas and principles about testing software are true for all software, not merely the code that will run in front of customers or the APIs that make things happen. Any software built for a purpose needs to be tested against that purpose, including the software running our test automation. |
|
“How Was This Tested?” Providing Evidence of Your TestingMany testers have a tendency to minimize the information they record when testing. The challenge comes when problems are found later, possibly after the software is in production. How do we remember what we did, and when? What records do we have to refer to? How do we, as testers, answer the question “How was this tested?” |
|
Considering the Value of Software Testers Many people think software testing is just about verifying from a checklist that functions do or do not appear. But what if more testers spent time looking at the product's behavior? Testers working with product owners, a development team, and other stakeholders can compare their understanding of the software and ask the crucial question, “Will this meet our needs?” |