>>>> Aside from test automation, efficiency can also be improved by streamlining the various components of the process. This includes test environment setup, test data retrieval, and test execution. Release cycles tighten and so should the testing processes.
I feel Partial Automation is very effective way of carrying out the QA process in an organization. With rapidly changing UI many a times it just wastes engineers time in automating some component which becomes obsolete faster than the time it consumed to get implemented.
Looking into streamlining the QA process and automation I found, getting sanity test automated in first stab makes life lil easier. For both the engineer who is automating it and for the testers, who can off load some work from their back.
Also doing the formal code review with QA automation engineers helps them in understanding what part qualifies for automation. Which might help in building an effective partial automation.
I very much appreciate the general message. I could give a lot of examples when only the combination of human interaction and automation yields economic results. (a testmanager)
Yes, Partial Automation definitely is an effective way of carrying out the QA Process. The Automation Tools can Automate the process and make things faster and manytimes easier but humen interaction and intelligence always needed to yield the correct and useful results.
Well, I recently built a decent software-based solution to partial automation (I think!) that would allow to minimize the impact of human intervention into the automated process. I can't call this a framework, but it manages the capability to run automated scripts, while allowing to seamlessly switch between automated and manual modes of execution. I will soon start posting information on this into my personal website - http://www.my2pie.com/blog (I'll need some revamping of my site, before I can do this, and might sometime). If you can't hold you questions, please look up my profile and write to me directly.
On the topic of partial automation, I agree its helpful, and done well can offer a first pass/stage of testing to alleviate the amount of manual testing required (reduce manual testing scope to areas of importances based on partial automation test results, etc.)
But that also requires management buy in. In the past, I had suggested to an organization adding partial automation to our automation suite to gain additional test coverage, even though it would not be full coverage with automation, it didn't get buy in, because to them it was either go big or go home. They don't want incremental improvements. :(
This comment has been removed by the author.
ReplyDeleteIn reply to this openion:
ReplyDelete>>>> Aside from test automation, efficiency can also be improved by streamlining the various components of the process. This includes test environment setup, test data retrieval, and test execution. Release cycles tighten and so should the testing processes.
I feel Partial Automation is very effective way of carrying out the QA process in an organization. With rapidly changing UI many a times it just wastes engineers time in automating some component which becomes obsolete faster than the time it consumed to get implemented.
Looking into streamlining the QA process and automation I found, getting sanity test automated in first stab makes life lil easier. For both the engineer who is automating it and for the testers, who can off load some work from their back.
Also doing the formal code review with QA automation engineers helps them in understanding what part qualifies for automation. Which might help in building an effective partial automation.
I very much appreciate the general message.
ReplyDeleteI could give a lot of examples when only the combination of human interaction and automation yields economic results.
(a testmanager)
Yes, Partial Automation definitely is an effective way of carrying out the QA Process. The Automation Tools can Automate the process and make things faster and manytimes easier but humen interaction and intelligence always needed to yield the correct and useful results.
ReplyDeleteWell, I recently built a decent software-based solution to partial automation (I think!) that would allow to minimize the impact of human intervention into the automated process. I can't call this a framework, but it manages the capability to run automated scripts, while allowing to seamlessly switch between automated and manual modes of execution. I will soon start posting information on this into my personal website - http://www.my2pie.com/blog (I'll need some revamping of my site, before I can do this, and might sometime). If you can't hold you questions, please look up my profile and write to me directly.
ReplyDeleteOn the topic of partial automation, I agree its helpful, and done well can offer a first pass/stage of testing to alleviate the amount of manual testing required (reduce manual testing scope to areas of importances based on partial automation test results, etc.)
ReplyDeleteBut that also requires management buy in. In the past, I had suggested to an organization adding partial automation to our automation suite to gain additional test coverage, even though it would not be full coverage with automation, it didn't get buy in, because to them it was either go big or go home. They don't want incremental improvements. :(