RE: In general, how do you see automation fitting into...
When the given project is not so large or the repetation work in the project is not so hard then there is no need of Automation tools.But if the given SRS is too large and the repetation work is quite large also it can be said that repetation work is a very tedious job. And we feel that there is a less chances of bug finding using manual then automation tool is very much needed
RE: In general, how do you see automation fitting into...
Automation Testing or Manual testing is dependent on certain factors like Requirements Time of the project Budjet etc If the Project is small and doesnot involve any repetitive tasks then it is best to choose manual testing.If the project has many builds released for every few days then it is difficult to check all the aspects of the application.Automation Testing Speeds up the testing process. We can create test Scripts that checks all aspects of the application and then we can run these tests on each new build.Benefits of Automated Testing:- Reliable Reapetable Fast Programmable Comprehensive Reusable.
RE: In general, how do you see automation fitting into...
Joytsna u r absolutely perfect....
Usually for small project we never go for automation ( say 1 year ) bcoz automation takes around 8 times effort of manual testing.So whenever project is small its better not to go for automation and if the features are changing frequently then also don't preffer automation and whenever there is lack of expert for verification point of view its better not to go for automation and also for no clarity of the requirement.
SO go for automation whenever test cases or features need to be tested repetatively ( for almost all builds ).At that point we can do testing in faster rate than manual once the script is ready.
RE: In general, how do you see automation fitting into...
Automation is done for the larger projects where the requirements are clear and defenitive.It is suitable where there is no continuous changes in the requirement.Automation is not done for the entire project.Automation is done only for the certain modules in which large amount of data transaction is involved.For regression testing automation is preffered.
With respect to the performance load and stress 90 of the projects are done by automation.
RE: In general, how do you see automation fitting into...
Automation is useful in following types of testing/scenarios:-
(1)If some bach programs needs to be run at night then automation allows unattended execution of the tests at high speed.
(2) Suppose tests are to be used in regression again & again then automating those test cases makes sense since tests will be reusable & repeatable.
(3) Data driven testing - same test cases are to be run for thousands or miliions of records then there is no point manually carrying out the same test steps with different data sets instead tester can use xml spy/ excel & make a parameter file from which data can be fed in to the driver thus automation comes into picture.
(4) You know certain tests are benchmark tests which are to be run again & again with every version then they can be seperately kept in a test suit & the whole test suite can be automated.
(5) As all know stress load volume these tests are good candidates for automation since they need many virtual users.
