Should automation code be as complex as application code?



  • Software project are often created as modules (in separated project folders) and communicate using services and apis to communicate between modules in order to improve flexibility and scalability.

    Should software test automation projects echo the structure of the application in test?

    That is, would they use the services and APIs the application uses, and if they do, to what extent? Is there a recognized best practice in test automation of large, complex application?



  • Should an automated testing project be created complex as much as software being developed?

    Probably, I would handle test-code the same as production-code. It should be as complex as it needs to be. It should be just as maintainable and understandable.

    Upto what extent a software automation project use these services and modules etc techniques?

    When it needs it. Similar to any software project. Simple and small projects might not need it, large code-bases probably will.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2