Manual, QTP and Selenium Testing

What is JavaScript? JavaScript was designed to add interactivity to HTML pages JavaScript is a scripting language A scripting language is a lightweight programming language JavaScript is usually embedded directly into HTML pages JavaScript is an interpreted language (means that scripts execute without preliminary compilation) Everyone can use JavaScript without purchasing a license -------------------------------------------------------------------------------- Are Java and JavaScript the Same? NO! Java and JavaScript are two completely different languages in both concept and design! Java (developed by Sun Microsystems) is a powerful and much more complex programming language - in the same category as C and C++. -------------------------------------------------------------------------------- What can a JavaScript Do? JavaScript gives HTML designers a programming tool - HTML authors are normally not programmers, but JavaScript is a scripting language with a very si...

Where to Put the VBScript Scripts in a page will be executed immediately while the page loads into the browser. This is not always what we want. Sometimes we want to execute a script when a page loads, other times when a user triggers an event. Scripts in the head section: Scripts to be executed when they are called or when an event is triggered go in the head section. When you place a script in the head section you will assure that the script is loaded before anyone uses it Click here for more on VB script

What is VBScript? VBScript is a scripting language A scripting language is a lightweight programming language VBScript is a light version of Microsoft's programming language Visual Basic How Does it Work? When a VBScript is inserted into a HTML document, the Internet browser will read the HTML and interpret the VBScript. The VBScript can be executed immediately, or at a later event. How to Handle Older Browsers Older browsers that do not support scripts will display the script as page content. To prevent them from doing this, you can use the HTML comment tag:

Automated testing provides a methodical and more intense way of testing the requirements and business processes. It brings many benefits which are summarized as follows: Facilitator in change adaptation: Automated testin provides speed to the testing phase of a complex and critical requiremnets thereby assisting in not only testing of multiple variations in a given scenarios but also extending testing depth to include non routine test conditions. It gives confidence to the organizationals ability to adapt SAP business solution to the changes in the business environment in the specific time frame. High Resuability: The testin effort is sabed by using resuable tests thus enabling personnel to find and fix more errors. The resuability benefits also enables to build libraries of repeatable test assets and are particularly helpful in project rollouts and the regression testing at the country/region level. It also aids in bringing standardization across geopraphies for a company havin...

The testing approach should satisfy the following criterions: 1.simple to follow 2.Easy to create and maintain test scripts 3.covers business processes a combination of the following two approches are likely to provide best results in a SAP environment: A.Functional Decomposition Approach B.Modular Approach. B.Modular approach: It starts by creating a recording of exection of manual transaction, which is a part of the business process. A transaction forms the script or a segregated step(also called module)of the testing chain. All the transactions that form the overall business process are captured and linked together. the output of one transaction serves as input to subsequent one. thus, with user defined external data the entire business process can be executed automatically. The results along with errors if any are documented in the test log and are available to users.

In a SAP support environment, the maintenance and support activities are regulated by the change management procedures defined in an organization. The changes would be released periodically as per release calendar to productive environments and should be tested and aprroved beforehand. The following testing would be applicable: Integration testing for the changes :The changes as a part of chnage managment would be linked to the business process and the changed functionality can be tested quickly and comprehensively fo the end-to-end business process using automated testing. The test cases should be well defined for the objects or process that is to be tested. Custom Developments should also be covered with the required test cases as these are often chaged because os bugfixes or enhancement. This would result into faster turnaround of the changes. Regression Testing: Regression testing is performed before the project go-live if it is rolling onto an existing productive system. The...

Testing during project life cycle: The Tenure of the project and the number of Roll-outs forms the criterions whether the project life cycle testing should be automated or not. If the automated scipts already exists, the same may be fine tuned for the said projects/Roll-outs. For the new projects and Rollout the following testing cycle can be automated: Project-Unit testing: This can be intitally manual during the build/development cycle but subsequently can be automated.It will aid in saving time and effort if changes and new requirements are introduced during project execution cycle. At this stage, both individual and combined test scripts can be used for the SAP transactions that form unit testing cycle. If the automated scripts already exists, the owner of the automated testing scripts can provide already validated scripts for the current and future projects. Project integration Testing: Automated testing can be helpful in integration testing cycle for projects. However, t...

The below figure explains the systematic representation of the areas of deployment for automated testing:It is important to identify what part of the testing processes would be automated. The enterprise application, which are subjected to change either because of maintenance or project go-live, are most suitable for automated testing.

Automated Testing has assumed significance as it is seen as a tool which can be used by the organizations to attain and maintain the competitve advantage. It helps to react quickly in a structured way to the changes in business processes which are enabled by various enterprize applications and legacy systems. The customers can shop anytime and from anywhere in a global environment and this had put the pressure on the organizations to make the business solution robust,scalable and available. Automated testing helps in acheiving these objectives.

QA Analyst  XXXXX(NAME),QA email@email.com XX Any Street XXXXXX XX 90000 (000) 000-0000 Senior QA Analyst with expertise in all phases of testing for client/server and Web applications SUMMARY OF QUALIFICATIONS Over "X" years of QA experience in all phases of life cycle, including requirements gathering, risk analysis, project planning, scheduling, testing, defect tracking, management, and reporting. Adept at using both manual and automated testing tools to troubleshoot systems, integration, user acceptance, positive and negative, functionality, object, and regression Develop use cases, user interface specifications, and user requirement specification documents. Liaise with developers, business analysts, and user representatives in application design and document reviews. Superior analytical, troubleshooting, communication and presentation skill. TECHNICAL SKILLS Testing Tools : QuickTest Pro, LoadRunner, Test Director, Visual Source Safe, Visual Intercept,...

What Is GUI? A computer user interface is the place where machine and human being communicate with each other. It is how we tell computers what we want and how they present to us the information we request. Today, the most common user interfaces involve a keyboard, viewscreen, and, more and more often, a mouse. A graphical user interface is a computer-user interface that uses graphical screen images as well as typed text,with icons on the screen replacing many of the functions of the keyboard. For example, in a typed text interface, the command to move data from one file to another is typed into the computer as a line of code meaning, Send this letter from file A to file B.” In GUI, a user might send this command by placing the cursor on the letter (represented by the image of an envelope), and moving it with a mouse across the screen from file A (represented as a rectangle), to file B(represented as another rectangle). Click the mouse, and the transfer is complete. Many sighted peo...

You will now run the ActionB test. The entire test will run only once, but the FlightOrder action will run twice; one time for each set of data in the Copy of FlightOrder data sheet. Run the ActionB test. Confirm that all Web browsers are closed. Click Run or choose Automation > Run. The Run dialog box opens. Select New run results folder and accept the default results folder name. Click OK. When the test run is completed, the Test Results window opens. Examine the test results. Examine the Results Summary. The test is marked as Done. This indicates that the test ran without any failures (there were no checkpoints to "pass"). Expand Test ActionB Summary > ActionB Iteration 1 (Row 1) in the Test Results window. Select the Copy of FlightOrder Summary action in the results tree. Note that within the summary, the results of both iterations are displayed. Close the Test Results window. Choose File > Exit to close the Test Results window.

If you look at the Data Table at the bottom of the QuickTest window in the ActionB test, you will see four tabs: Global, Copy of FlightOrder, Sign_in [ActionA], and ReturnHome [ActionA]. Note: If the Data Table is not displayed, choose View > Data Table to display it, or click the Data Table button . The Global tab is a data sheet whose data is used for the entire test. If five rows of data are displayed in the Global table, the test will run five times. In addition, you can create data sets for each action, using the relevant action sheet. If you parameterize a step using an action parameter and enter five rows of data in the corresponding sheet, you can define that action to run five times within each test iteration. Note: The Sign_in [ActionA] and ReturnHome [ActionA] data sheets are displayed in gray and cannot be edited because each of these data sheets belong to the corresponding called action and can be edited from the called action's original test only. In t...

Now, you will insert a copy of the FlightOrder action. Confirm that the ActionB test is open. If not, choose File > Open > Test. Browse to ActionB and click Open. Insert a copy of the FlightOrder action. Choose Insert > Call to Copy of Action. The Select Action dialog box opens. Click the browse button next to the From test box. Select the ActionA test in the Open Test dialog box, and click Open. The actions from the ActionA test are displayed in the Action List. Select the FlightOrder action. Note that the description of the selected action is displayed in the Action description box. In the Location area, select At the end of the test. Click OK. The Copy of FlightOrder action is added to the end of the test. Note that the call to the copy of the action you inserted is just like any other action call in your test. You can modify the steps in the call to the copied action just as you would those of any other action call. Modify the Copy of FlightOrde...

First, you will insert calls to the reusable Sign_in and ReturnHome actions from ActionA into ActionB. Open a new test   . For more information, see step 1 of Recording a Test. Insert a call to the Sign_in action. Choose Insert > Call to Existing Action. The Select Action dialog box opens. Click the browse button next to the From test box. Select the ActionA test in the Open Test dialog box, and click Open. Note that only reusable actions from the ActionA test are displayed in the Select Action dialog box. Select the Sign_in action. In the Location area, select At the end of the test. Click OK. The call to Sign_in [ActionA] action is added to the end of the test as a call to an external action with the icon. Note that you cannot expand the Sign_in action call in the test flow in the Keyword View. To view the steps in the Sign_in action, select it from the Action List. The action call you inserted is read-only. To modify the action, you must open the origin...

When you plan a suite of tests, you may realize that each test requires one or more identical activities, such as signing in. Once you have created the action and stored it with one test, you can insert either a call to a copy of the existing action, or a call to the existing action, into other tests. When you insert a call to a copy of an existing action, you can make changes to the copied action, and your changes will neither affect, nor be affected by, any other test. Calls to existing actions, however, are read-only in the calling test. They can be modified only in the test in which they were stored. Calls to existing actions enable you to call the same action from several tests and make it easy to maintain tests, because when your application changes you only have to update the existing action stored with the original test. In the following exercises you will create a new test that is similar to the ActionA test, except that the Sign_in and ReturnHome actions are external act...

Reusable actions are like functions in programming. When you have a process that you may need to include in several tests, you record, modify, and enhance the steps of the process and save them in a reusable action. Then you can call the action from other tests, rather than recording, modifying, and enhancing the same steps each time. To call an action from another test, you must make it a reusable action in the test with which it was stored. The Sign_in and ReturnHome action you created in this lesson can apply to almost any test you might create on the Mercury Tours site, so it makes sense to make them reusable actions. Make the Sign_in action reusable. In the Keyword View, right-click the Sign_in action and choose Action Properties. The Action Properties dialog box opens. Select the Reusable action check box and click OK. If a message box is displayed, read the message, click Do not show this dialog box again, and click OK. The action icon changes to a reusable action icon . ...

Now you will insert a call to a new action and record the step of returning to the Mercury Tours home page so that the entire test begins and ends on the same page. Insert the ReturnHome action. Choose Insert > Call to New Action or click the Insert Call to New Action button . The Insert Call to New Action dialog box opens. Enter ReturnHome in the Name box, confirm that At the end of the test is selected, and click OK. The dialog box closes and the ReturnHome action is added to the end of your test. Prepare the application for recording. Confirm that your Web browser is open to the Flight Finder page. If your browser is not open, open it to the Mercury Tours site (http://newtours.mercury.com) and sign in. The Flight Finder page opens. Position the applications on your desktop so that you can see both QuickTest and the Web browser. Change the Record and Run settings. Currently, your Record and Run settings are set so that a new browser opens each time you begin reco...

Here i explained how to divide the test into two actions. Follow the below steps: Since your test currently contains two main processes: signing-in and purchasing a flight, it makes sense to divide the test into separate actions. 1. Select the page where you want the second action to begin.  In the Keyword View, expand Action1 > Welcome: Mercury Tours. 2. Split the test into two actions . Select the first Find a Flight: Mercury page and choose Edit > Action > Split Action or click the Split Action button . The Split Action dialog box opens. 3. Enter names and descriptions for the two actions. In the Name box of the 1st action type: Sign_in. In the Description box of the 1st action, type: Enters user name and password to sign in. In the Name box of the 2nd action type: FlightOrder. In the Description box of the 2nd action, type: Chooses and purchases a flight. Click OK to close the Split Action dialog box and accept the other default selections....

As you know how to record the new test. Eventhough i explained below how to record the test for creating new actions: Start QuickTest and open a new test . For more information, see step 1 of Recording a Test. Start recording on the Mercury Tours Web site. In the coming steps, you will record a test similar to the one recorded in the Recording Tests lesson. However, this test is designed slightly differently to optimize the test for a multi-action test. Confirm that all Web browsers are closed.  Choose Automation > Record or click the Record button . The Record and Run Settings dialog box opens. In the Web tab, select Open the following address when a record or run session begins. Confirm that the URL in the first box is http://newtours.mercury.com and in the second box, choose a browser on which to run your test session. Confirm that the Do not record and run on browsers that are already open and Close the browser when the test closes options are selected. I...