Software testing and Automation of APIs with UFT/QTP

Advance your API testing skills with UFT 11.5 in part two of the quick test professional tutorial, exploring GUI interactions and hands-on API testing techniques.

Learn to link steps in UFT to create a flow for api testing, adjusting the step name in the properties pane general tab, using a multiply two numbers example.

Explore the UFT tools pane to drag actions into the test, perform operations like addition and multiplication, and add custom code or a report message action with a user-friendly interface.

Explore the UFT canvas pane, focusing on the test settings tab, test input-output, and test variables tab to manage API scenarios, inputs, outputs, and events before and after execution.

Learn to pass the output of one action as input to the next in UFT/QTP by linking results between steps, using custom expressions, and validating with a checkpoint.

Explore creating and running an api test step, use the report message event to log pass or fail, inspect results in the output window, and verify checkpoints against expected values.

Link the report message to dynamic variables such as localhost name and test variables, and display who is running the test at the start of the run.

Review the quick general overview from part two, learn how APIs work and how to interact with UFC, API and its new GUI interface, then start web services testing.

Join this session as we introduce the next topics in UFT, start interacting with UFT, and test SOAP-based web services while building foundational terminology for API testing.

Understand soap web services and the wsdl, and test them using UFT/QTP. Import the wsdl, list methods, pass values, invoke methods, and verify correct responses through positive testing.

Explore positive testing of web services with UFT/QTP, validating that services return correct values for given inputs and invoking methods after importing a WSDL.

Generate a positive web service test case by sending an IP address to a soap service, validating the country name and code returned, and parameterizing tests for multiple values.

Test web services to ensure they return end user expected data, such as country code and country name, not irrelevant values. Log bugs for scripting errors and issues.

Use timers to measure how long a web service takes to respond and identify acceptable response times for the software you are developing.

Test how web services handle unexpected loads using load testing with virtual users to observe response and stability under stress. Recognize that applications may crash when user demand spikes.

Perform negative testing by supplying invalid values, such as a string instead of an IP address, and observe how the web services respond to invalid input, including boundary testing.

Set up an API test checkpoint to validate geo IP data, return codes, and country name from a SOAP response, comparing actual to expected values.

Learn to test web services with http requests, rest and soap considerations, and set up and run an http test in UFT/QTP, including viewing captured results.

Explain how an http request works and why it powers rest and soap. Identify the three parts: the request line, headers, and body, and how they enable client-server communication.

Explore the anatomy of http requests by examining get, post, port, and delete, plus trace, options, head, and connect, with headers and bodies explained in a simple get example.

Explain the http request–response cycle, identify status code ranges from 100–199 to 500–599, and examine examples like 200 status, 404 not found, and 500 server errors.

Understand how http requests from a client elicit rest api responses, use get to retrieve data, and test status codes like 200 and 404 while contrasting soap and rest.

Balance pace and practice to master API and GUI testing in UFT/QTP, avoid rushing, and leverage hands-on study to connect concepts and build on-the-job mastery.

Illustrates how soap web services are brittle due to a rigid client–server contract, making changes require a new service version and pushing us toward rest services.

Contrast soap web services with rest and restful testing, noting decline of soap and the rise of rest API testing for faster, higher-value outcomes.

Introduce rest APIs as a lightweight web service approach that uses the http protocol, favors json data, and contrasts rest with soap, highlighting noun-verb data modeling and hierarchical metadata.

Explore how REST defines resources and uses HTTP methods to login, logout, and retrieve user data, including creating a user with POST and querying session balance via URIs.

See how a REST service exposes app functionality through APIs, explore authorization constraints that limit actions like listing users, and validate JSON responses with key-value pairs and arrays.

Explore how to query a restful API URI, validate and organize JSON responses, and retrieve data such as posts, taxonomies, and descriptions by modifying the URI parameters.

Learn how a restful URI uses a resource path and query string to perform get, post, delete, and update operations, returning JSON with key-value pairs and real-world examples.

Learn to test and protect restful apis by exploring the query string and how search terms affect api responses, using dev tools to observe security implications.

Set up a rest uri in UFT, create a rest api test for Google Books, define a query books resource with get method, and run the test to view results.

Run a REST API test, view the request and response data, and format the JSON response with json.org for readable key–value pairs.

Learn to navigate a JSON response by accessing properties and values, drill into arrays like items[0], and retrieve fields such as id and Shakespeare's volume within an API context.

Test APIs manually using the chrome Postman extension to craft GET, POST, PUT, and DELETE requests and validate endpoints with real responses.

Open the toolbox, locate the rest api service, right-click to add or edit it, and modify the method or add methods to update the api in UFT.

Practice what you learned as you proceed with REST API testing in UFT. Build tests and real-world skills, avoid rushing, and ask questions to master API automation.

Learn why APIs should be tested, see real test scenarios, and follow a practical API testing progression to build automated tests from day one for your career.

Master api testing skills as demand rises while gui testing declines; this course prepares you to meet the industry's evolving needs and advance your career.

Explore the flight API sample for automated API testing with UFT/QTP. It covers SOAP and REST interfaces, including get, create, reserve, update, and delete operations using XML or JSON.

Explore why api tests are growing in popularity, as api testing runs in milliseconds, far faster than gui tests, and review the automated testing pyramid in practice on uft/qtp.

Explore automated testing pyramid: unit tests at base, API tests in middle, GUI tests at top, and why unit and API tests deliver the most value early.

API testing reduces test case creation time, boosts ROI, and aligns with the testing pyramid by prioritizing REST API tests over GUI tests in the toolbox.

Test APIs early in the lifecycle to reduce bug-fix costs before the GUI, and see how applications communicate through restful interfaces, with Facebook-style posting as an example.

Explore the two-tier RESTful architecture where applications use restful interfaces to update back-end systems, enabling the GUI to consume APIs and promoting early API development and testing.

API testing grows in demand as GUI testing declines; learn to test APIs end-to-end using UFT/QTP and build tests from start to finish, enhancing application quality.

Explore a practical testing progression for API and automated testing, from smoke tests to regression, negative, boundary, security, and load tests, with examples for when to test.

Perform rapid smoke tests to validate deployment and API health, confirming the app loads or that an API returns a response or error code within 30 seconds.

Open a UFT environment, troubleshoot solution access, create a new UFT solution for learning, and launch the API application to continue testing.

Start the API service in UFT by running the Flight API sample, use the help index, and prepare an automated test against the Flight API and Mercury Tours website.

Get familiar with the flights api by exploring rest resources, using get to list all flights and fetch flight details, and perform a smoke test before reserve order post method.

Learn how to add a REST service to a UFT test, model API documentation with flight orders and reserve order, and configure the REST flights API with a base URL.

Model an API test in UFT by creating a post request for the reserve order endpoint, using the flight orders path from documentation, with an XML or JSON body.

Set up a quick smoke test for a rest api using a get on a flight resource. Verify a 200 response and detect failures when the service is down.

Set up a quick smoke test with UFT to verify the API is up by validating HTTP status codes and then build a reusable test suite focused on database-related operations.

Learn how to use create, read, update, and delete (CRUD) operations in API testing, applying them as smoke tests to validate deployment and core functionality.

Reserve a flight order using a post, which returns the order number and total price. Set headers for content type text xml (or json) and define input and output checkpoints.

Model the input properties of a REST API in UFT/QTP by defining XML elements for class, customer name, departure date, flight number, and number of tickets with appropriate types.

Model the response by defining output properties such as order number and total price, and execute the test to observe the service response.

Master running a create method using UFT in API testing, verify the response status and inspect order number and total price, then add the step to the test canvas.

Move a REST service from local to a global repository by right-clicking and moving it to filesystem activities, making it available to other tests.

Configure a get flight order method using the API documentation, set a relative url with a hard-coded order number, and insert the XML response sample in UFT.

Upload an xml file into the UFT response body and load xml to auto generate the schema, then validate flight order values such as John Doe and checkpoints.

Create an update action in UFT by defining a flight order update with a request body and its update request and response body, added to the smoke test suite.

Analyze a put request in postman to update a flight order, fix headers, set content type, and verify the update with a get to explain why the name didn't change.

Learn to use put and get calls on a flight API, verify updates by getting a flight's tickets, and troubleshoot partial updates while exploring the API documentation through hands-on testing.

Create a put request using UFT to update a flight order, set tickets to five, validate a 200 response, and relocate the method to rest/flight orders on the canvas.

Learn to create a test user, then delete it via the API delete method, verify the response, and use Postman to manage flight order data safely.

Learn to perform delete http requests in UFT to remove a flight order, verify deletion with a subsequent get, and handle responses like true or 400 bad request.

Save the UFT API test as a smoke test suite to quickly validate core API methods, automate in Jenkins, and review fast, reliable test results.

Explore the testing tree and data-driven approaches to software testing with UFT/QTP, showing how permutations across data types enable scalable automated and manual test coverage.

Explore negative test cases for string fields by passing non-string data, like integers, to ensure an appropriate error message appears and the api call is blocked.

Examine rest APIs handling of blank calls, empty strings, and null values; test boundary conditions, including 256-character limits, and use negative data to prevent crashes.

Explore validating APIs with UFT/QTP by testing string fields for all ASCII characters, performing boundary tests on integer ranges, and exploring security tests like SQL injections and cross-site scripting.

Explore testing strategies for primitive data types and dates, including boundary and negative tests, integration testing, and handling daylight savings time to prevent date-related failures.

Validate date fields by confirming accepted formats and performing positive and negative tests. Apply boundary and leap year checks driven by test data to cover all month days.

Move a UFT/QTP solution to a new location and fix missing tests by re-adding data driven API, smoke, and flight API tests. Clean up the solution to prevent future errors.

Explore data-driven API testing by using a spreadsheet to drive tests, focusing on the update method of a flight order to validate the tickets field response.

Ensure every automated test initializes and tears down its own data, avoiding reliance on other tests and preserving exact state.

Create a unique test case identifier in the spreadsheet to enable traceability and coverage for UFT tests linked to a user story.

Model the API and test data in UFT to data-drive tests, building a spreadsheet with four fields and an expected status code to cover multiple tickets and test scenarios.

Demonstrate designing UFT API test cases with clear naming, changing the tickets field to test invalid inputs, and asserting status codes above 299 for negative, string, null, and blank values.

Learn how to import an Excel sheet into UFT for a data-driven API test, creating a data table and linking it to a test action.

Learn to link an input parameter to a data table in UFT, sourcing the URL from a spreadsheet data source and validating post requests with status codes and descriptions.

Create a checkpoint in UFT using the status code from the data table's expected status code column and confirm it.

Parameterize the tab by linking flight number, customer name, class, and tickets in UFT, while addressing data type cautions and using a status code checkpoint.

Run a UFT API test by looping over data table rows, execute the test flow, and fix failures by enforcing status codes greater than 299.

Add a post action handler in UFT to flip a failed rest API test to a pass, using an event that sets status to success when the result is failure.

Learn how to add a post action handler in UFT and organize test data in one place within a folder structure to streamline automated testing and achieve successful results.

Learn to interpret UFT API test results by debugging failures, distinguishing between test errors and actual code defects, and using Postman and captured data to verify requests and responses.

Review UFT's API test results by examining captured data and checkpoints for pass or method not allowed in post requests, then share reports for daily status updates.

Explore load testing and security testing in API testing, discuss tools like load runner and the realities of testing progression, including login functionality and the role of load tests.

Test caching and concurrency with UFT by combining create and read steps to verify data persistence, then design data-driven negative and boundary tests for APIs.

Explore automated testing with UFT API, covering how web services use SOAP over HTTP, the structure of HTTP requests and status codes, benefits of API testing, and smoke tests.

Explore automated testing of rest APIs using uft/qtp, learning what rest is, how to create and use rest services, and validate results with postman.

Explore automated api testing with UFT/QTP: learn the testing progression from smoke tests to crud tests, with an api-centric pyramid, test trees, and diverse negative, boundary, and security cases.

Wrap up by sharing notes, reattaching tests, and appreciating your time; commit to daily practice to become a proficient automation engineer in software testing.