it looks like my time on blogging decreases day by day. I have less and less time to think up and then write something novice and interesting on test automation. Is it writer's block? Or Summer? :))))
Inspiration will come but not today and may not in this month, so far I imbibe, learn and think. This post is just a bunch of technical and organizational things as conclusions and generalization on accumulated posts.
While I'm preparing a presentation for high-management, want to share some pieces of that. The below diagram represents test automation infrastracture as whole picture to highlight scope of works and to inspire feel of confidence that we provide really professional test services and use advanced techniques and practices upon building the entire and completed automated system.
Another image represents our secured approach of code developement - nothing new - just following proper development practices.
Wherever you automates testing, it's suggested to invest in the best development practices that will return the investements down the road depending on project duration and long-term purposes.
Some of that truly should be applied for serious test automation (formerly the posts of this blog):
ROI on automation testing department establishment
On stabilization test suites. No fuel but destination is too far
Naming and coding conventions: are they important for test automation?
Source control and change management in test automation
Test Automation Dashboard in just One day!
20 Essential design patterns for automated testing
Adopting TDD practices into white-box test automation
Measuring test (manual/automation) effectiveness
Lastly some things on organizational approaches and practices