I have
been thinking of writing a blog for quite some time. Have been procrastinating for quite a while around this. I was not sure in terms of what to write and how will it be perceived but I thought
let me take a plunge. This is my take on all things test automation and many
different things around testing and tools.
My
first blog is around a Mind map which I had put around Test Automation. It is titled Test Automation- Can Do and Don`t Do''. The idea of this mind map came
when I was asked for short paragraph for what automation can do as well as what
type of automation may not be pursued. I put together a paragraph around this
and tried to explain both points. It was becoming too descriptive and verbose.
I thought I should put a mind map about this topic which will give a single
view for this topic.
Test
Automation -Ø
Automation
Can Do following
- Improve Accuracy of Test Execution and Verification by elimination of Human errors
- Reduce the execution time by automating repetitive tasks
- Reduce Time to Market by Reducing Test Execution Time there by reducing test cycles
- Increase the Test Coverage by covering more data combinations
- Triggering the Test Execution at Specific Time Interval
- Saves screen prints of execution for future audit trails
- Tedious Activities like Data Setup and Data Comparison can be automated by reducing wait Time for Testers by automating Data Setup activities
Test Automation Ø
Don`t
Do Automation When
- Unstable application
- Frequently changing functionality
- Rarely used functionality
- Test scenarios with unpredictable results
- Look & Feel and Usability of application
- Too Complex
This not an exhaustive list of all 'Can Do' and 'Don`t Do' automation scenarios. I will try to add the scenarios in both context.
