10 rules for writing automated tests

By Oren Rubin

Our customers often ask for our guidance in building their test suites properly. Performance, ease of management and scalability were key priorities for them. We decided to share our suggestions with a broader audience.

We came up with the list while building our own test suites. Since we strongly believe in "eating our own dog food", Testim is tested using Testim. We also learned a lot from working with a variety of companies from small startups to large enterprises.

Rule 1: Prioritize
Rule 2: Reduce, Reuse, Recycle
Rule 3: Create Structured, Single-Purpose Tests
Rule 4: Tests’ Initial State Should Always be Consistent
Rule 5: Compose Complex Tests from Simple Steps
Rule 6: Add Validations in Turnover Points
Rule 7: No Sleep to Improve Stability
Rule 8: Use a Minimum Two Levels of Abstractions
Rule 9: Reduce the Occurrences of Conditions
Rule 10: Write Independent and Isolated Tests
##Click here to read the full article.