Back

Barriers to automation

  • Legacy code – With software documentation often outdated or non-existent, it can be hard to start writing scripts for automation with no context of user requirements. The danger here could result in writing automation scripts against what the system is doing rather than what it should do.
  • Investment – Businesses often do not commit to automation because they do not understanding why they need to invest in it. Their pressure is getting the product out in the market with as little expense as possible. The problem here is understanding the return on investment that can be provided with automation testing.
  • Team commitment – Often testing the current sprint deliverables are prioritised ahead of the automation tasks and time for creating automation scripts is difficult to schedule and manage.
  • Continuous maintenance – As with any solution or product, for it to effectively work it needs to be well looked after. Where improvement is due it needs to be looked at with as much importance as a user story. This can mean that there needs to be a dedicated person looking after the health of the tool.

Recommended Further Reading

The following materials may assist you in order to get the most out of this course:

Translate »