Watch Paul Grizzaffi’s expert webinar, as he makes the point that automation development is software development, and takes us through the ins and out of why, and how, to perform code review on automation code.
Breaking! Automation development is software development. Yeah, it’s true. Even if we are using a drag-and-drop or record-and-playback interface to create automation, somewhere in the stack, under the hood or behind the curtain, there is code that was sequenced by our actions. We must start treating our automation initiatives as software development initiatives, lest we wind up in a quagmire of unsustainability.
One beneficial tactic used in software development is to have a team member go through newly written or modified code, looking for issues and risks; this is called a code inspection or code review. Much as a proofreader or editor will provide feedback on a book or article, code inspectors provide feedback on areas of the code that may benefit from rework, such as supportability, readability, extensibility, and issues or risks of issues.
In this in-depth webinar, Automation Expert Paul Grizzaffi takes us through why we should do code inspections of our automation software, how inspections for automation can differ from those for product software, and actual issues found during these reviews.
Watch this webinar, and enjoy these key takeaways:
— Automation development is software development – treat it as such
— Consider this our “second pair of eyes”
— Let business value drive how we inspect code
— There are tools to help us with review-related activities – use them