Clean Code Practices for

Test Automation

Any fool can write code that a computer can understand. Good programmers write code that humans can understand.

- Martin Fowler

Clean Code

Simple & Elegant

Easy to Enhance

Efficient

Better readability

Elegant

No duplications

Dispensables

/* TODO: Refractor it later. Harcoded for now. */

Bloaters

Single Responsibility Principle

Open Closed Principle

“Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification.”

Clean Code for Test Automation

By Srinivasan Sekar

Clean Code for Test Automation

  • 305