Shulou(Shulou.com)06/03 Report--

Because of the project, some time ago, I studied and used the SoapUI test tool for self-test development of api. The following will show you the results of the research, hoping to help those in need.

What is SoapUI?

SoapUI is an open source testing tool that checks, invokes, and implements functional / load / compliance testing of Web Service through soap/http. The tool can be used as a separate test software or integrated into Eclipse,maven2.X,Netbeans and intellij using plug-ins.

Installation of SoapUI

Download address, it is best to download the latest version of the installation package, because SoapUI is based on java development of the test tool, version 3.0 installation package does not integrate JRE, so you have to install and configure the java runtime environment.

The use of SoapUI

1. In the File menu of the main interface, click "New REST Project" and fill in the url you want to test. According to the url in our project Teacher Site, for example: https://teacher-test.grapecitydev.com:

Refer to the following figure to enter the / Login/Login route in the Resource input box, and enter the query parameters accountName and password required for login in Params.

two。 Click the green button, SoapUI sends the login request, and you can see the result returned by the login request in the right box.

According to the business requirements of the Teacher site project, you have to send the SchoolItemChange API after sending the Login request before returning the authenticated Token after the user logs in successfully. The value of Set-Cookie in the following figure will be used in the Cookie attribute in the request header of the next GetOverview API:

3. The next third request GetOverview is shown in the figure below. Add the Cookie attribute in the Header box, and the value is the Set-Cookie value returned by the previous request SchoolItemChange:

Automated testing

In fact, the call of the above three interfaces is simply to test whether the call of the interface is normal. If you want to test the calls of the three interfaces automatically, please see the following decomposition:

1. Right-click the Request request under each interface, as shown in the figure, select the "Add TestCase" item, set TestCase for the above three interfaces in turn, and there are three TestCases of Login,SchoolItemChange,GetOverview under TestSteps.

two。 Have you noticed that there is an extra Set Cookie item under Test Steps? what is this for?

This is to get the return value of the previous request (in this case, the return value of the SchoolItemChange API "Set-Cookie") through the Groovy Script syntax, and assign the "Set-Cookie" attribute value to the request header Cookie of the next request GetOverview, doesn't it fit in with the second and third request?! This solves the problem of automated testing of the interface without having to copy and paste the dependent return values between requests.

3. Next, you need to add the Assertion assertion for the tested interface. Click on the bottom left corner, and the Add Assertion dialog box pops up. According to the assertion annotation, select the desired test point. For example, Response SLA indicates the expected response time after the request is sent:

Contains Assertion indicates that the string returned by the request contains the specified string. This assertion applies to no more than 65535 characters, because Soapui is written in the java language, which is the maximum number of characters supported by jvm:

4. To solve the above problem of no more than 65535 characters, you need to add Script Assertion to the interface. The following code indicates that the content in the local file GetOverview 01.txt is compared with the value of the HtmlOfPartialView attribute in the request return to determine whether the two contents are equal:

5. Double-click TestCase, as shown in the following figure, click the button, or select Login right-click to select "Run from here", then execute the Test Steps step in turn. As shown in the figure, the red background Failed appears. Check the TestCase Log box in the lower right corner. You can see that the response time 1272ms of Step 4 GetOverview API request is greater than the time 500ms set in the assertion:

Send mail function

When you want the result of an API request to be notified to you by email, as shown in the following figure, right-click Test Steps-> Add Step-> Groovy Script, and add a Send Email script, where Username and Password are the account and password of the company mail server, and Internet Address is the receiving email address.

The order of "${teacher-test#TestCase#Getoverview#Response}" is

Test Suite name # Test Case name # Test Step name # Response:

Pressure testing

The above is the functional test, and then there is the stress test. Right click Load Tests to create the test case.

Limit:60 is the time of stress test. 60sPowerThread means multi-thread. It can run 5 threads at the same time. Test Delay * Radom indicates the number of time delays randomly.

Min represents the minimum response time, max represents the maximum response time, avg represents the average response time, last represents the last request response time, cnt represents the number of requests per second, tps represents the number of requests processed per second, bps indicates throughput, and rat represents error rate.

Right-click to add assertions to the request, Max Errors sets the maximum number of errors, Step Average sets the expected aPCge time, and so on:

As shown in the following figure, you can select load and performance tests for different policies:

The most commonly used is the simple strategy (Simple), if you want to run functional tests and want to delay 5 threads in 10 seconds, then Threads is set to 5, delay 1000s, random delay ratio 0.5 (about to cause a delay of 5 to 10 seconds).

Variance policy (Variance), Threads is the number of threads of variance, and Interval sets the required value for the interval. For example, if you set 20 threads with an interval of 60 and a variance of 0.8, the number of threads will increase from 20 to 36 in the first 15 seconds, then decrease to 20 and 45 seconds, and then return to the initial value of 20 at 60 seconds. It is easy to follow this variance in a statistical chart:

Linear policy (Thread), the number of runs from one thread to another. Its main function is to determine the level at which certain statistics change or events occur, such as setting start and end thread values (for example, 1-10), and setting the duration (in this case, at least 30 seconds per thread) to obtain accurate measurement data:

Continuous integration

For continuous integration in the UI interface: right-click the project name REST Project 1-> Select Launch TestRunner, as shown below, and select the TestRunner installation path on the Basic Tab page:

Select the report output folder on the Reports Tab page:

Click the Launch button to execute the test project automatically.

For continuous integration by executing the command, open the Command Prompt dialog box as an administrator and execute the following command:

Testrunner.bat-cLogin tester-cLogin-r-j-FullD:\ Trivals\ SoapUI\ Logs' D:\ Trivals\ SoapUI\ REST-Project-1-project.xml

The parameters of the command line have the following meanings:

S: The TestSuite to run, used to narrow down the tests to run

C: The TestCase to run, used to narrow down the tests to run

R: Turns on printing of a small summary report (see below)

J: Turns on exporting of JUnit-compatible reports, see below

F: Specifies the root folder to which test results should be exported

For more parameter settings, please refer to the SoapUI official website address:

Https://www.soapui.org/test-automation/running-functional-tests.html

This article briefly introduces the basic use of the SoapUI tool, and you are welcome to leave comments to supplement the more multi-functional use of SoapUI to learn and make progress.

Reprint, please indicate from: grape city control

The welfare of the grape city at the end of the year is in hot delivery.

Users who purchase team authorization and enterprise authorization of Grape City controls before December 31, 2017 can not only enjoy preferential prices, but also receive customized training services provided by Grape City technical experts according to the needs of customers' projects. Old customers recommend new customers into an order, and they will also receive a "double gift of customer recommendation".

Learn more: http://www.gcpowertools.com.cn/order/specialoffers.htm

About Grape City

Founded in 1980, Grape City is the world's largest control provider, the world's leading provider of enterprise application customization tools, enterprise reports and business intelligence solutions, serving more than 75% of the world's Fortune 500 companies. Grape City set up an R & D center in China in 1988, constantly adapting to the local needs of the Chinese market in the process of global product research and development, and providing excellent software tools and consulting services for the informatization of software enterprises and various industries.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.