Developers don't help the automation team

From Test Automation Patterns
Revision as of 14:18, 24 April 2018 by Cathal (talk | contribs) (Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px">Please select what you think is the main reason for the lack of support from developer...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Please select what you think is the main reason for the lack of support from developers:

For the following items look up issue INADEQUATE COMMUNICATION
  1. Developers think that since they are writing (and executing) unit tests there is no need for system level automation
  2. Developers don't see any reason why they should do "extra work" (e.g. naming objects) - why spend effort to help the automation which doesn't help me?


More reasons why developers don't help:

  1. Developers don't have time because they have an enormous load of work to execute. The issue AD-HOC AUTOMATION should give you a good start on how to manage this problem
  2. Developers don't realize that for instance changing components can completely disrupt automation. Look up issue NO INFO ON CHANGES



Return to "Lack of support"