Automation dependably takes after manual testing. Ordinarily, at least one rounds of manual testing as of now would be performed on the Application under test. This means manual test cases currently exist and have been executed at any rate once as an automation scripts.

Anyway the software product, a few measures of manual regression and functional tests can be automated. There are various outlines of automated test scripts over all stages and working frameworks, and paying small notice to what sort of system is being tested, it justifies looking for after that target.

The more fundamental functional structure and inauspicious regression tests can be automated, the more manual testing projects with test cases can focus on business work forms, defect examination, negative conditions and diverse opening and-corners that can turn a framework from normal to hearty.

To be sure, even with a determination to automation scripts, regardless, the best approach to changing over manual test cases can be frustrated before you even begin if the manual testing test cases are not composed in a way to deal with make them automation scripts. The automation scripting tools uses manual test cases as a blueprint to forming code. The arrangement is pointless if the writing manual test cases are indefinite, lacking subtle element, or too much broad.

The accompanying are the rules we will take after to accomplish the translation of Manual Test Cases into Automation Scripts:

1. State of the AUT: The segment precondition is only a specific condition of the foundation to be set for a specific advance to be executed.
2. Test Steps: We can order the manual test steps into three groups:

Information section – Data passage steps are the place you are entering some data as a contribution to your AUT.

Change of AUT state steps – these means are the ones that will make a change happen to your AUT. It may incorporate going another page, a specific field being unmistakable, an alter box being editable and so forth.

Combination – as the name suggests, this is mix of both of the above sorts. Take the instance of a checkbox, when turned on will make a specific field dynamic. All things considered, you are entering the esteem “Valid” for the checkbox field and it likewise brings about a condition of your AUT.

3. Automation steps:

Information section steps are not altogether different in the automation test script and manual techniques. Everything you do is entering the information. The way you reference the field is unique. Since it will be machine playing out the means, we simply need to ensure we allude to the fields in the AUT in a way that the device gets it. That implies, you need to utilize its consistent name as utilized as a part of the QA test scripts.

For Change of AUT/Combination sample test cases for beginners in a manual situation, you play out the action and confirming the change at one go. However in automation situation that isn’t conceivable. So we need to ensure we include steps for action and approval/check.

4. Remarks for readability.

Debugging declaration – these are particularly vital which you are making and testing the test itself. Attempt to utilize message boxes regularly to yield different esteems at different phases of test execution. This will give you perceivability into the test like nothing else would.

Result proclamations – to write to comes about or some other outside place like a scratch pad or exceed expectations sheet.

Verification and Validation

Without check and approval the purpose of testing is lost. Commonly you should utilize test cases for web application in manual testing. So you should utilize a ton of restrictive articulations and furthermore circle proclamations to fabricate the rationale.

5. Test Data

The accompanying is a portion of the inquiries that you should seriously consider responding to your sample test cases for manual testing requirements:

• Where to put it?
• To hard code or not?
• Security concerns?
• Reusability concerns?

When you glance back at the manual test script, you will see that having the test information, the username and password accessible is one of the preconditions to try and start the test.

6. Results

For a manual test case, you can put the consequence of each progression in the “genuine outcome” section. An automation tool’s outcome record contains the aftereffect of each progression when executed.

Post Operations

When you are finished with testing it requires not be expressly specified in your manual test case to close the program or close the AUT and so on. As a tester, you would do it determinedly. On account of automation test scripts, you can incorporate these means in your script. Moreover clean up – is the thing that I call these actions. Execute every one of the associations you made. Close all the applications. Discharge the memory.

So, you perceive how effectively an automation script unfurls when you have elegantly composed manual scripts and an arrangement of fundamental rules to take after.  Test content being the crucial building square, it is easy to extemporize on a script when you have the good knowledge of how to automate test cases using selenium, how to write automated test scripts in java as well as agile test scripts.