SarahS
Staff
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Scripting in ReadyAPI Virtualization for Dynamic Mocks
Here's an example on mapping values from a data source into a response message. This example reads in an Excel file, then uses a request parameter as a key value to find the values of a row of data in the Excel spreadsheet. There's another example on the SoapUI documentation that discusses how to do this with a database connection. You can navigate here for that example. This script is broken down into three sections. The first section reads in the request parameter that we'll use as our key. Request parameters can be accessed with the mockRequest.getRequest().getQueryString() methods. I take the output of this method and tie it to a string. You'll want to do some parsing on the string to isolate the exact value you want to use. The second section then opens a workbook in Excel and looks for the row of data based on our key (the "q" property). The POI libraries make it fairly easy to work with Excel workbooks, and there's lots of resources online that can explain how to use the libraries better than I can. All we're doing here is opening the workbook and scanning each row to see if we find a row of data that matches our key. The third section triggers if we find a row of data that matches our key. I use a switch statement here to map the values of the row to a property. The main thing to note is that we use the requestContext.value format to assign the values to a virtual service property. Here's the script I use: //Read in excel libraries import org.apache.poi.ss.usermodel.* import org.apache.poi.xssf.usermodel.XSSFWorkbook //================================================================// //Part 1. Read in request parameters. //================================================================// // Get the query string of the request, isolate the "q" parameter // In this example, the request string looks like: "q=CityName&apikey=abc1234" def inputString = mockRequest.getRequest().getQueryString() def inputString2 = mockRequest.getRequest() log.info inputString2 def q = null //split query string def keyValuePairs = inputString.split("&") keyValuePairs.each { pair -> def key = pair.split("=")[0] def value = pair.split("=")[1] if (key == "q") { q = value } } //================================================================// //Part 2. Open Workbook. Scan for row of data //================================================================// // Specify the path to your Excel file def filePath = "<path to your file here>" // Specify the value to search in the first column def searchValue = q // Load the Excel file def file = new File(filePath) def workbook = new XSSFWorkbook(file) // Assuming the data is in the first sheet, you can change the sheet index if needed def sheet = workbook.getSheetAt(0) // Find the row with the matching search value def matchedRow = null for (Row row : sheet) { def cellValue = row.getCell(0)?.toString() if (cellValue == searchValue) { matchedRow = row break } } //================================================================// //Part 3. Map cells of the row to response variables. Close workbook. //================================================================// if (matchedRow != null) { for (Cell cell : matchedRow) { int columnIndex = cell.getColumnIndex() switch (columnIndex) { case 0: requestContext.cityCell = cell.toString() break case 1: requestContext.countryCell = cell.toString() break case 2: requestContext.abbrCell = cell.toString() break default: break } } }else { //Do Something } // Close the workbook workbook.close() The response then looks like this: { "Response": "This is a dynamic response", "Location":"${cityCell}", "Country" : "${countryCell}", "Country Code" : "${abbrCell}" } My example uses a spreadsheet which provides responses for the 50 most populated cities. As long as we hit a city on this list we'll return a response such as this: The dataset that I'm using in this example looks like this:Re: Scripting in ReadyAPI Virtualization for Dynamic Mocks
Below is a scripted example on taking the content of a payload in a POST request and routing the JSON nodes into a virtual response message. To read in the values of the request body I use the mockRequest.getRequestContent() method. This will return a string value that may include some extra content along with the request payload. You'll likely want to trim the extra content out so that the payload is extracted from the original string. Once we have the payload isolated, we can create a JSON slurper to easily extract the content of the JSON nodes. The nodes are then tied to a property value that I reference in the response message using the requestContext.value format, where value is the name of the property that we'll reference in the response. //Add slurper to isolate json. This makes it easier to parse the nodes in the response import groovy.json.JsonSlurper //Save the response content to a string //This will result in some overhead def logText = mockRequest.getRequestContent() // Find the index of the first '{' character def startIndex = logText.indexOf('{') // Extract the substring starting from the '{' character def result = startIndex != -1 ? logText.substring(startIndex) : logText //pipe the result into a json slurper for easy parsing def jsonSlurper = new JsonSlurper() def JsonBody = jsonSlurper.parseText(result) //We can map the individual nodes from the Json object that we created previously requestContext.id = JsonBody.id requestContext.categoryID = JsonBody.category.id requestContext.categoryName = JsonBody.category.name requestContext.name = JsonBody.name requestContext.status = JsonBody.status The response will then look like this: { "Message": "Successfully read in payload", "Values": { "ID": "${id}", "Category ID": "${categoryID}", "Category Name": "${categoryName}", "Name": "${name}", "Status": "${status}" } } The result should look like this:Scripting in ReadyAPI Virtualization for Dynamic Mocks
Hey Everyone. I wanted to make a post about scripting in ReadyAPI Virtualization for the purpose of creating dynamic mocks. Scripted samples always help when I'm trying to achieve something, so I hope that these scripts will help guide you with dynamic mocks. I've primarily used two resources to learn how to work with dynamic mocks. The first is a support document for SoapUI OS. This page has a comprehensive overview on working with mock services and provides examples on how to accomplish various tasks when working with the virtual service scripts. https://www.soapui.org/docs/soap-mocking/creating-dynamic-mockservices/ The second resource that I've found to be useful is our documentation on Virtual service scripting.I find that this page is better than the previous one above at explaining the scripting objects that ReadyAPI uses. here:https://support.smartbear.com/readyapi/docs/virtualization/configure/scripting.html My intent here is to provide some scripted samples that I've worked on. I'd also like to hear if anyone has requests on scripted tasks with virtual services in ReadyAPI.Re: Run Test Cases via Groovy Script
HiUser999, I don't have a groovy script example for you. I do have some non-scripted ideas that you could work with. The first is to create multiple data sources and loops within the same test case. For each data source you can identify the target rows to run. Within the data source loop you can run the individual test steps to target. Then when that loop finishes you can then run another data source loop for the next test steps. The second idea would be to use the Run Test Case test step. The Run Test Case test step runs a test case from your project as a test step. You can find information on this here.Re: Double iteration over data source
I would have assumed that you could reference the same data source with a second data loop as well. It doesn't appear to be the case. I'll look into this a bit more. In the meanwhile, alternative options that we could explore would be to have one data loop that implements the delete operations. The second would be to use a second data source. You could clone the original data source and create a second group that references the clone.Re: Fixed rate strategy in ReadyAPI
HiKuroosa, Fixed rate load profiles/strategies are still supported. Added screenshots taken in the latest (3.44.0) version of ReadyAPI of the fixed rate for performance tests. Would it be possible for you to provide a screenshot to this thread of what your ReadyAPI UI looks like? Might be able to provide more information based on what you're experiencing.Re: Parse multi line response
Heystuartbarber, It looks like your'e selecting a response node. What we need to do is select the entire response instead. To do this, we can use GetData and choose the target Response property from your SOAP request. You'll be prompted to select a response node on the following screen. Don't select any of the nodes. Pressing 'OK' without selecting any individual node will reference the entire response. This will store the response as the screenshot below demonstrates. You could also refer to the response using the following format:${SOAP Request#Response} , where SOAP Request is the name of your target request.Re: Floating license?
ihorstep Floating licenses come with a number of seats. Each floating license seat will allow one user to access ReadyAPI. Let's say your team has 10 people and you purchase 3 floating licenses. This means there are 3 floating license seats this allows up to 3 users to access ReadyAPI concurrently. You can assign all ten users to use these floating licenses. If 3 team members are consuming the three seats then the remaining 7 members of your team will not be able to access a floating license. Let's use the screenshot on that page as an example. This floating license has 10 seats assigned to it. So up to 10 users can consume floating licenses at any given point in time. If an 11th user attempts to access to ReadyAPI they will be unable to retrieve a license until one of the 10 users are disconnected. Does this help?Re: How to iterate throw Excel data in a groovy script?
HiTaz, Understanding that your goal here is to use the entire data set in a script. One approach I can think of would be to read in each row of data and perhaps pass this into an array. The syntax for referencing a row is as follows: ${DataSouceTestStep#DataSourceProperty::RowNumber} You can use a property/variable as the RowNumber to iterate through the data set. Documentation for this is here if you want to get more details. https://support.smartbear.com/readyapi/docs/functional/steps/data-source.htmlRe: data source Loop
Hiarmygrad, There's not a lot of information here, but if I had to guess I would say your test case is aborting on error and an error is occurring on data loop 7. If this is the case then you can un-check the option for aborting the test case on failure in your test case options. Or you can go to Preferences and apply this for all your test cases by default. If this isn't the issue could you provide some additional information? It might be helpful to see whats happening in the transaction log around loop 7.
