Test Automation Change Control Process – Sounds Interesting?


This change control process is to ensure that in a "big" automation project whenre "Modular" Library architecture is followed, libraries are not mistakenly / intentionally changed by the automation testers and every change in the library goes through a well defined "Automation Workflow" depending upon the role and the access rights.

Changing libraries without this process can even cause the other automation scirpts to fail or having a possibility of redundant code being written for same functionality which is often the reason for automation failure.

Thought of depicting this process graphically so that everyone here can understand this process.


Library Change Control Process
 

Comments (1)

  1. Aditya Kalra says:

    Hi Raj,

    I liked the graphical representation, gives a clear picture of test Automation Change Control Process

    This surely makes it a candidate on my blog which has the best articles and posts across the web.

    Do mail me at aditya_kalra@ymail.com and let me know if it is fine i add this to my blog.

    My blog: go-gaga-over-testing.blogspot.com

    Best Regards,

    Aditya Kalra

Skip to main content