CodeX
Published in

CodeX

Automated testing patterns

Testing patterns serve the goals of automated testing: specification, documentation, support for refactoring, and help in locating defects.

Creating patterns to describe something creates nomenclature. Once you have a name for something, it’s easier to recognize when you see it again. The Productive Programmer

I’ll present the testing patterns that I apply in every project since they’ve proven very beneficial to the team concerning the goals of automated testing

--

--

--

Everything connected with Tech & Code. Follow to join our 900K+ monthly readers

Recommended from Medium

Twitter-Biggest dataset that is open

How to participate in the Big Bang Round

Automated Acceptance Testing with Cucumber, Protractor, and Selenium on Angular 8 application

Tortle Ninja Development Update | Sprint 26

Vaiden MS 50x150x12 steel building prices 601 936 5293

Understanding Cost, Usage and Query Administration on Snowflake

Join the smart economy — Create Your Own NeoContracts. Part II. Tools.

Designing a Travel API for Analytics — Further Considerations

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Luís Soares

Luís Soares

I write about Lean, TDD, CI/CD, trunk-based dev., user-centric dev, DDD, coding good practices, testing

More from Medium

“A Beginner’s Guide To Software Testing” [Part-3]

Difference Between Test Case And Test Scenario

Behavior Driven Development, Cucumber, BDD with Cucumber.

Time to automate localization testing.