Free training announced by KM Ridge

For details mail me to ukonda@kmridgetechnologies.com

or call me at 9912898097

Free Training for Fresher with placement guarantee

Dear Sir/Madam,

This is Umashankar, Director KM Ridge Systems Private Limited a corporate training and recruitment firm.  KM Ridge is having more than 2 years in the field of corporate training and providing the training for SEI CMM level -5 companies like Wipro, Accenture, CTS, CNO IT services, FSS and TATA ELXSI. We are also working in the field of recruitment.

Currently there is a requirement of 50 Software Test engineers for one of our client, which is a CMM Level 5 company in Bangalore.

Educational Qualifications:

• BSc, BCA
• Above 60% from 10^th to Graduation
• Good communication skills

Training:

• We will provide the training for one month
• 8 hours a day
• Fully practical oriented with 3 projects

For further details contact Umashankar konda, 9912898097, ukonda@kmridgetechnolgoies.com

Urgent requirement of software test engineers for 2 to 5 years of experience

About us: KM Ridge systems private limited is a training and placement company from hyderabad. KM Ridge is expert in providing the training solutions based on the client requirement on software testing. KM Ridge is providing trainings to CMM level 5 companies including Wipro, Accenture, CTS, TATA ELXSI and many more.

Client: Cleint is a SEI-CMM Level 5 company having offices in India and other 150 countries. In india they have offices in multiple locations including hyderabad, bangalore, Delhi, mumbai and Pune.

Requirement: Software Test engineer - Automation
Experience: 2- 5 years
Skills: Manual Testing, SQL, Oracle/MS SQL server, QTP/RFT/Selenium
Good Communication skills

Education: BE/BTech/MCA, with 60% throughout from 10
Role: Software Test engineer - Automation

Responsibilities: 
1. Writing test cases from the requirements
2. Test execution
3. Developing automation test scripts
4. Review test scripts
5. defect reporting and tracking
6. Coordination with team members and development team

if you are interested in this opportunity
send your resumes to uknda@kmridgetechnologies.com

To connect a database and get the records from database

Set cnn = CreateObject("ADODB.Connection")
   cnn.ConnectionString = "driver={SQL Server};server=<enterserver>;" & _
      "uid=<enterlogon>;pwd=<enterpassword>;database=<enterdatabase>"
   cnn.Open
   If cnn.State = adStateOpen Then
      cnnState = "open"
   Else
      cnnState = "closed"
   End If

set rs=createobject("adodb.recordset")

mySql = "Select * from Tab_name"

rs.open sql,cnn

' To print all the column names

for i=0 to rs.fields.count-1

print rs.fields(i).name

Next

'to print all the values for each column
for i=0 to rs.fields.count-1

Print rs.Fields(i).value

rs.moveNext

Next

'close the connection

cnn.Close

cnnState = "closed"

Test to choose cheapest flight for inset order

the below program will work to chose cheapest flight
Add the objects to the test before  executing this code

Window("Flight Reservation").Activate
Window("Flight Reservation").WinObject("Date of Flight:").Type "121212"
Window("Flight Reservation").WinComboBox("Fly From:").Select "Denver"
Window("Flight Reservation").WinComboBox("Fly To:").Select "Frankfurt"
Window("Flight Reservation").WinButton("FLIGHT").Click

FlightCount = Window("Flight Reservation").Dialog("Flights Table").WinList("From").GetItemsCount()
FlightDetails = Window("Flight Reservation").Dialog("Flights Table").WinList("From").GetItem(0)
'msgbox FlightDetails

flights = split(FlightDetails,"$")
TempPrice = flights(1)
flight=0
For i=0 to FlightCount-1
FlightDetails = Window("Flight Reservation").Dialog("Flights Table").WinList("From").GetItem(i)
'msgbox FlightDetails
flights = split(FlightDetails,"$")
price = flights(1)

If Price<=Tempprice Then
flight = i

End If
'msgbox flight
Next
FlightDetails = Window("Flight Reservation").Dialog("Flights Table").WinList("From").Select(flight)
Window("Flight Reservation").Dialog("Flights Table").WinButton("OK").Click
msgbox FlightCount&" "&FlightDetails
Window("Flight Reservation").WinEdit("Name:").Set "test"
Window("Flight Reservation").WinButton("Insert Order").Click
Window("Flight Reservation").Activate
Window("Flight Reservation").Restore
Window("Flight Reservation").WinObject("Insert Done").Check CheckPoint("Insert Done")

How to work with Actions in QTP

Ways of creating the Actions:

1.       Creating the Action During Recording

2.       Creating the actions after recording

Navigation:

Go to insert menu à Select “Call to New Action” à Enter Action Name à Description à check the check box “Reusable Action” to make the action reusable à select location as At End of test or after current step. (Generally we will use the first option)

External Actions: A reusable action “xyz” created in test X, called into Test Y then, that ‘XYZ[testX]” is external action to “Test Y”, which cannot be edited. It is read only in “Test Y”.

Call to Copy Of Actions:

If an action is called using “Insert à Call To Copy of action”, the entire action will be copied to the current test along with its resources. The advantage is it can be modified according to your current test requirements. But, it increases the utilisation of memory. Use whenever necessary.

These modifications applicable to current test only.

Eg:

Action_Login created as reusable in testX

Called copy of Action_Login in to TestY - à COPY Action_Login or you can modify to Action_Login

You modify the Action_Login of TestY. This modification does not affect Action_login of TestX.

But, IF you call “Action_Login of TestY into TeSTA, then in TestA, you will get the Action_Login of TestY along with its modifications.

Split Actions:

An action can be split in Two Actions at a time.

Navigation for Split Action:

1.       Enter new line from where the action to be split

2.       Right Click à Select Actions à click Split Action à Select “Independent of Each Other” or “Nested Actions”

3.       Enter Names for Action 1 and action 2

what are the different types of actions in QTP?

Actions:

A test can be divided in to multiple logical units called as Actions. This helps in easy maintenance.

Types of Actions:

1.       Reusable Actions – These can be used by any of the test. It can re-use within the test it created and also in the other tests.

2.       Non – Reusable Actions – can’t be reused even in the test it is created.