Approach to Functional Automation Testing Traditional Approach
Functional Automation Testing
Traditional Process:
Functional testing is termed as process that is used to test an application end to end manner or a specific zone on the below written parameters..
- Accurate
- Reliable
- Predictable
- Secure
This is a quality assurance process to verify if the requirements are deployed correctly into the system and working as it is supposed to do.When we test a large software , we might take traditional waterfall model or V model or an incremental model .
Functional Automation Testing
Prior to final release it will undergo different releases.Now if you look at from testing perspective the initial testing is purely manual.It is smooth too. Problem happens when bug got fixed in the earlier releases and also new feature is getting added to the latest release.
Test engineers need to make sure the bug fix is ok. No regression bug has been introduced during this bug fix and new feature is working well!!!!
To fix a bug and test regression test engineers need to test all test cases prior to current release. They need to write new test cases as well.
So what we can do..
Functional Automation Testing
- Either increase no of test engineers
- Increase the timeline
Lets say we have started a testing process with 3 members and in the subsequent releases we plan to add 2 resources to mitigate the risk of testing new features.
Now after 5th release…the no become..3+2+2+2+2=11 series formula
an=a1+(n-1).d=3+4.2..
Functional Automation Testing
So if you have more 10 releases the testing resource cost become very high.You need to consider the training cost of the new resource and time factor for the new test engineers to produce quality bugs.
On the other hand most of the time the timeline gets squeezed due to bug fix late development. lack of test planning.So increment in timeline is very hard.
Last both the approach is leading to heavy cost or less testing future.
Cost graph-
