"Automation or Manual testing"

While this seems to be quite abnormal if you ask in what we want typo to work before coming to the testing carrier. In Hyderabad, the teaching culture of software testing has changed/seems to be changed a little bit like previously it was a struggle between our friends(upcoming testers) that automation means QTP, win runner etc where I used to object that though this is not the means but just to have a regular basis discussion. When I was into this testing carrier I asked a lot of people (An upcoming testers) about these two terms “Manual testing or automation testing”, every time we start we do have a several arguments and in the end we do have nothing but just to smile on each other faces which makes that we are an upcoming testers.
In my basis Automation is just an added skill to the Tester, but not just that it is the world. Without the manual there is no automation and off course there are vice versa in some cases. Automation itself is not just the tools like “QTP, Win runner, Silk runner” etc. the point is what ever we needed in our regular basis used for testing purpose that reduces time is an automation.. this was the basic of Automation testing.
I do like to give few examples. Let’s have field something like this

FIELD ONE

Conditions : Only 2000 characters will allow.

In such kind of test cases what would someone will do. I saw few people who started to write 2000 characters in a notepad. Which was a waste of time, in order to save time we do have lots of tools like test data generator. Search for them and generate 2000 characters which would prominently save time and increase the productivity. Such tools help us a lot in increasing productivity. Another small example is WORD/emails where we have a spell checker, which is an automated tool where we correct the wrong spellings.
Automation is not just the tools like QTP or win runner, Typically one has to be understand that what ever is needed for automating to increase our productivity is an Automation tool.

NOTE : DEAR UPCOMING TESTER’s This post is especially to increase awareness about the automation or manual. I would really happy if at least one got understood from this post and implement in your daily basis to increase your productivity and don’t forget to leave your comments before you go away from this blog.

SOME OF THE AWSOME SITE :
you will never leave once you are visit these as at some point or the other you always need to increase your productivity

www.testingmentor.com
www.testersdesk.com

Working with STAF (part 2)

Well we have discussed some of the concepts of staf in post WAORKING WITH STAF. NOW we will have some thing interesting interaction by using JMeter.

Now let us know the concepts of Jmeter inorder to go further.

JMeter is a open source tool we can download from the site Apache Jmeter.
Jmeter is a performance tool used for finding the avg. response time, devaition etc parameters like the other tools load runner. The only use of the Jmeter is a open source and also it is a less memory eater when compared to the other tools.

NOW create a test plan according to the manual given in the Apache Jakarata site site itself, After creating a test plan save the file with desired name. LETs go to STAF now.

IF for suppose this file is in the remote system. we can execute this file and and the results can be obtained in our systems. INORDER to do this we have to give the trust levels to the remote systems. There are 5 trust levels, according to each trust level the access is differnet for the remote systems. After giving the trust level. Now we can execute the test plan by making a batch file.

In this Batch file we need the controller where the system we handle load generators where the test case is present, Well, i will make batch file very simple to understand and an idea how to execute the test plan by using the batch file.

REM set the controllers
REM set the load generators
REM set the plan

SET controller= webserver1
SET load = webserver2
SET plan=myplan.jmx

REM checking the STAF connecting to the remote systems

FOR %%H IN (%controller% %load%) DO STAF %%H PING PING

REM executing the test plan using jmeter

for %%H IN (%load%) Do staf %%H PROCESS START SHELL COMMAND C:\jmeter\bin\jmeter-n.cmd C:\jmeter\bin\myplan.jmx

REM copying the results from the remote system to our system

for %%H IN (%load%) Do staf %%H fs copy directory c:\jmeter\bin todirectory c:\logs\ tomachine %controller% EXT log CASEINSENSITIVE

This is a small batch file where we can use staf and make wonders.