`

soapUI test

 
阅读更多
declare namespace xmlns='${#Project#host}/TestDirectory/api/v1.0/automationrule/1';
/xmlns:Response/xmlns:automationRule/xmlns:id



<automationRuleReturn>
   <status>OK</status>
   <automationRule>
      <id>1</id>
      <buildTargetId>2</buildTargetId>
      <buildTargetName>MIPS Linux</buildTargetName>
      <deviceSubtypeId>1</deviceSubtypeId>
      <priority>5</priority>
      <projectId>1</projectId>
      <projectName>project</projectName>
      <softwareComponentId>1</softwareComponentId>
      <softwareComponentName>PRoject MFL/log</softwareComponentName>
      <testFolderId>10</testFolderId>
      <testFolderName>MFL LOG CI</testFolderName>
      <type>CI</type>
   </automationRule>
</automationRuleReturn>

1. 判断返回的状态
automationRuleReturn/status
OK

2. 判断返回的ID
automationRuleReturn/automationRule/id
1

3. 判断返回的类型
automationRuleReturn/automationRule/type
CI




<automationRuleReturn>
   <errorNumber>INVALID_REQUEST</errorNumber>
   <errorText>Create AutomationRule[com.technicolor.project.common.core.exception.InvalidRequestException: Invalid Request: Type cannot be null]</errorText>
   <status>NOK</status>
</automationRuleReturn>


1. 错误信息匹配
automationRuleReturn/errorText
Create AutomationRule[com.technicolor.project.common.core.exception.InvalidRequestException: Invalid Request: Type cannot be null]





<Response xmlns="http://10.11.59.83/TestDirectory/api/v1.0/automationrule/1">
   <automationRule>
      <buildTargetId>2</buildTargetId>
      <buildTargetName>MIPS Linux</buildTargetName>
      <deviceSubtypeId>1</deviceSubtypeId>
      <id>1</id>
      <priority>5</priority>
      <projectId>1</projectId>
      <projectName>project</projectName>
      <softwareComponentId>1</softwareComponentId>
      <softwareComponentName>project/log</softwareComponentName>
      <testFolderId>10</testFolderId>
      <testFolderName>MFL LOG CI</testFolderName>
      <type>CI</type>
   </automationRule>
   <status>OK</status>
</Response>

1. 通过命名空间判断返回的状态
declare namespace xmlns='${#Project#host}/TestDirectory/api/v1.0/automationrule/1';
/xmlns:Response/xmlns:status
OK

2. 通过命名空间判断返回的值
declare namespace xmlns='${#Project#host}/TestDirectory/api/v1.0/automationrule/1';
/xmlns:Response/xmlns:automationRule/xmlns:id
1


<Response xmlns="http://10.11.59.83/TestDirectory/api/v1.0/automationrule/1">
   <status>OK</status>
</Response>

declare namespace xmlns='${#Project#host}/TestDirectory/api/v1.0/automationrule/1';
/xmlns:Response/xmlns:status
OK




<automationRuleListReturn>
   <status>OK</status>
   <automationRuleList>
      <automationRule>
         <id>351</id>
         <buildTargetId>10</buildTargetId>
         <buildTargetName>SIP Server MP GoLinux</buildTargetName>
         <deviceSubtypeId>12</deviceSubtypeId>
         <priority>1</priority>
         <projectId>16</projectId>
         <projectName>CPE_ANT_R8.C.S</projectName>
         <softwareComponentId>266</softwareComponentId>
         <softwareComponentName>vdnt-s</softwareComponentName>
         <testFolderId>100</testFolderId>
         <testFolderName>TF 1P2</testFolderName>
         <type>OFFICIAL</type>
      </automationRule>
      <automationRule>
         <id>350</id>
         <buildTargetId>10</buildTargetId>
         <buildTargetName>SIP Server MP GoLinux</buildTargetName>
         <deviceSubtypeId>12</deviceSubtypeId>
         <priority>1</priority>
         <projectId>16</projectId>
         <projectName>CPE_ANT_R8.C.S</projectName>
         <softwareComponentId>266</softwareComponentId>
         <softwareComponentName>vdnt-s</softwareComponentName>
         <testFolderId>10</testFolderId>
         <testFolderName>MFL LOG CI</testFolderName>
         <type>NIGHTLY</type>
      </automationRule>
      <automationRule>
         <id>341</id>
         <buildTargetId>23</buildTargetId>
         <buildTargetName>vdnt-o</buildTargetName>
         <deviceSubtypeId>10</deviceSubtypeId>
         <priority>4</priority>
         <projectId>13</projectId>
         <projectName>Gateway Applications</projectName>
         <softwareComponentId>114</softwareComponentId>
         <softwareComponentName>vdnt-o</softwareComponentName>
         <testFolderId>341</testFolderId>
         <testFolderName>CLI_MBUS</testFolderName>
         <type>CI</type>
      </automationRule>
      <automationRule>
         <id>15</id>
         <buildTargetId>3</buildTargetId>
         <buildTargetName>Host Linux</buildTargetName>
         <deviceSubtypeId>3</deviceSubtypeId>
         <priority>3</priority>
         <projectId>2</projectId>
         <projectName>Project 2</projectName>
         <softwareComponentId>2</softwareComponentId>
         <softwareComponentName>Component 1P2</softwareComponentName>
         <testFolderId>100</testFolderId>
         <testFolderName>TF 1P2</testFolderName>
         <type>CI</type>
      </automationRule>
      <automationRule>
         <id>13</id>
         <buildTargetId>2</buildTargetId>
         <buildTargetName>MIPS Linux</buildTargetName>
         <deviceSubtypeId>1</deviceSubtypeId>
         <priority>3</priority>
         <projectId>2</projectId>
         <projectName>Project 2</projectName>
         <softwareComponentId>2</softwareComponentId>
         <softwareComponentName>Component 1P2</softwareComponentName>
         <testFolderId>100</testFolderId>
         <testFolderName>TF 1P2</testFolderName>
         <type>NIGHTLY_FOR_CI</type>
      </automationRule>
      <automationRule>
         <id>11</id>
         <buildTargetId>1</buildTargetId>
         <buildTargetName>x86 Linux</buildTargetName>
         <deviceSubtypeId>2</deviceSubtypeId>
         <priority>3</priority>
         <projectId>2</projectId>
         <projectName>Project 2</projectName>
         <softwareComponentId>2</softwareComponentId>
         <softwareComponentName>Component 1P2</softwareComponentName>
         <testFolderId>100</testFolderId>
         <testFolderName>TF 1P2</testFolderName>
         <type>NIGHTLY_FOR_CI</type>
      </automationRule>
      <automationRule>
         <id>14</id>
         <buildTargetId>2</buildTargetId>
         <buildTargetName>MIPS Linux</buildTargetName>
         <deviceSubtypeId>1</deviceSubtypeId>
         <priority>3</priority>
         <projectId>3</projectId>
         <projectName>Project 3</projectName>
         <softwareComponentId>2</softwareComponentId>
         <softwareComponentName>Component 1P2</softwareComponentName>
         <testFolderId>100</testFolderId>
         <testFolderName>TF 1P2</testFolderName>
         <type>CI</type>
      </automationRule>
      <automationRule>
         <id>12</id>
         <buildTargetId>1</buildTargetId>
         <buildTargetName>x86 Linux</buildTargetName>
         <deviceSubtypeId>2</deviceSubtypeId>
         <priority>3</priority>
         <projectId>3</projectId>
         <projectName>Project 3</projectName>
         <softwareComponentId>2</softwareComponentId>
         <softwareComponentName>Component 1P2</softwareComponentName>
         <testFolderId>100</testFolderId>
         <testFolderName>TF 1P2</testFolderName>
         <type>CI</type>
      </automationRule>
      <automationRule>
         <id>352</id>
         <buildTargetId>2</buildTargetId>
         <buildTargetName>MIPS Linux</buildTargetName>
         <deviceSubtypeId>1</deviceSubtypeId>
         <priority>5</priority>
         <projectId>1</projectId>
         <projectName>project</projectName>
         <softwareComponentId>1</softwareComponentId>
         <softwareComponentName>project/log</softwareComponentName>
         <testFolderId>100</testFolderId>
         <testFolderName>TF 1P2</testFolderName>
         <type>NIGHTLY_FOR_CI</type>
      </automationRule>
      <automationRule>
         <id>2</id>
         <buildTargetId>1</buildTargetId>
         <buildTargetName>x86 Linux</buildTargetName>
         <deviceSubtypeId>2</deviceSubtypeId>
         <priority>2</priority>
         <projectId>1</projectId>
         <projectName>project</projectName>
         <softwareComponentId>1</softwareComponentId>
         <softwareComponentName>project/log</softwareComponentName>
         <testFolderId>11</testFolderId>
         <testFolderName>MFL LOG QA</testFolderName>
         <type>NIGHTLY_FOR_CI</type>
      </automationRule>
      <automationRule>
         <id>355</id>
         <buildTargetId>10</buildTargetId>
         <buildTargetName>SIP Server MP GoLinux</buildTargetName>
         <deviceSubtypeId>12</deviceSubtypeId>
         <priority>1</priority>
         <projectId>10</projectId>
         <projectName>project Sync Rallydev</projectName>
         <softwareComponentId>266</softwareComponentId>
         <softwareComponentName>vdnt-s</softwareComponentName>
         <testFolderId>20000</testFolderId>
         <testFolderName>Test Folder For Performance</testFolderName>
         <type>CI</type>
      </automationRule>
   </automationRuleList>
</automationRuleListReturn>

1. 对多个item下面的节点进行判断其存在
exists(automationRuleListReturn/automationRuleList/automationRule[1]/buildTargetId)
true

exists(automationRuleListReturn/automationRuleList/automationRule[1]/priority)
true




<Response xmlns="http://10.11.59.83/TestDirectory/api/v1.0/automationrule">
   <automationRuleList>
      <automationRule>
         <e>
            <buildTargetId>10</buildTargetId>
            <buildTargetName>SIP Server MP GoLinux</buildTargetName>
            <deviceSubtypeId>12</deviceSubtypeId>
            <id>350</id>
            <priority>1</priority>
            <projectId>16</projectId>
            <projectName>CPE_ANT_R8.C.S</projectName>
            <softwareComponentId>266</softwareComponentId>
            <softwareComponentName>vdnt-s</softwareComponentName>
            <testFolderId>10</testFolderId>
            <testFolderName>MFL LOG CI</testFolderName>
            <type>NIGHTLY</type>
         </e>
         <e>
            <buildTargetId>10</buildTargetId>
            <buildTargetName>SIP Server MP GoLinux</buildTargetName>
            <deviceSubtypeId>12</deviceSubtypeId>
            <id>351</id>
            <priority>1</priority>
            <projectId>16</projectId>
            <projectName>CPE_ANT_R8.C.S</projectName>
            <softwareComponentId>266</softwareComponentId>
            <softwareComponentName>vdnt-s</softwareComponentName>
            <testFolderId>100</testFolderId>
            <testFolderName>TF 1P2</testFolderName>
            <type>OFFICIAL</type>
         </e>
         <e>
            <buildTargetId>23</buildTargetId>
            <buildTargetName>vdnt-o</buildTargetName>
            <deviceSubtypeId>10</deviceSubtypeId>
            <id>341</id>
            <priority>4</priority>
            <projectId>13</projectId>
            <projectName>Gateway Applications</projectName>
            <softwareComponentId>114</softwareComponentId>
            <softwareComponentName>vdnt-o</softwareComponentName>
            <testFolderId>341</testFolderId>
            <testFolderName>CLI_MBUS</testFolderName>
            <type>CI</type>
         </e>
         <e>
            <buildTargetId>3</buildTargetId>
            <buildTargetName>Host Linux</buildTargetName>
            <deviceSubtypeId>3</deviceSubtypeId>
            <id>15</id>
            <priority>3</priority>
            <projectId>2</projectId>
            <projectName>Project 2</projectName>
            <softwareComponentId>2</softwareComponentId>
            <softwareComponentName>Component 1P2</softwareComponentName>
            <testFolderId>100</testFolderId>
            <testFolderName>TF 1P2</testFolderName>
            <type>CI</type>
         </e>
         <e>
            <buildTargetId>2</buildTargetId>
            <buildTargetName>MIPS Linux</buildTargetName>
            <deviceSubtypeId>1</deviceSubtypeId>
            <id>13</id>
            <priority>3</priority>
            <projectId>2</projectId>
            <projectName>Project 2</projectName>
            <softwareComponentId>2</softwareComponentId>
            <softwareComponentName>Component 1P2</softwareComponentName>
            <testFolderId>100</testFolderId>
            <testFolderName>TF 1P2</testFolderName>
            <type>NIGHTLY_FOR_CI</type>
         </e>
         <e>
            <buildTargetId>1</buildTargetId>
            <buildTargetName>x86 Linux</buildTargetName>
            <deviceSubtypeId>2</deviceSubtypeId>
            <id>11</id>
            <priority>3</priority>
            <projectId>2</projectId>
            <projectName>Project 2</projectName>
            <softwareComponentId>2</softwareComponentId>
            <softwareComponentName>Component 1P2</softwareComponentName>
            <testFolderId>100</testFolderId>
            <testFolderName>TF 1P2</testFolderName>
            <type>NIGHTLY_FOR_CI</type>
         </e>
         <e>
            <buildTargetId>2</buildTargetId>
            <buildTargetName>MIPS Linux</buildTargetName>
            <deviceSubtypeId>1</deviceSubtypeId>
            <id>14</id>
            <priority>3</priority>
            <projectId>3</projectId>
            <projectName>Project 3</projectName>
            <softwareComponentId>2</softwareComponentId>
            <softwareComponentName>Component 1P2</softwareComponentName>
            <testFolderId>100</testFolderId>
            <testFolderName>TF 1P2</testFolderName>
            <type>CI</type>
         </e>
         <e>
            <buildTargetId>1</buildTargetId>
            <buildTargetName>x86 Linux</buildTargetName>
            <deviceSubtypeId>2</deviceSubtypeId>
            <id>12</id>
            <priority>3</priority>
            <projectId>3</projectId>
            <projectName>Project 3</projectName>
            <softwareComponentId>2</softwareComponentId>
            <softwareComponentName>Component 1P2</softwareComponentName>
            <testFolderId>100</testFolderId>
            <testFolderName>TF 1P2</testFolderName>
            <type>CI</type>
         </e>
         <e>
            <buildTargetId>2</buildTargetId>
            <buildTargetName>MIPS Linux</buildTargetName>
            <deviceSubtypeId>1</deviceSubtypeId>
            <id>352</id>
            <priority>5</priority>
            <projectId>1</projectId>
            <projectName>project</projectName>
            <softwareComponentId>1</softwareComponentId>
            <softwareComponentName>project/log</softwareComponentName>
            <testFolderId>100</testFolderId>
            <testFolderName>TF 1P2</testFolderName>
            <type>NIGHTLY_FOR_CI</type>
         </e>
         <e>
            <buildTargetId>1</buildTargetId>
            <buildTargetName>x86 Linux</buildTargetName>
            <deviceSubtypeId>2</deviceSubtypeId>
            <id>2</id>
            <priority>2</priority>
            <projectId>1</projectId>
            <projectName>project</projectName>
            <softwareComponentId>1</softwareComponentId>
            <softwareComponentName>project/log</softwareComponentName>
            <testFolderId>11</testFolderId>
            <testFolderName>MFL LOG QA</testFolderName>
            <type>NIGHTLY_FOR_CI</type>
         </e>
         <e>
            <buildTargetId>10</buildTargetId>
            <buildTargetName>SIP Server MP GoLinux</buildTargetName>
            <deviceSubtypeId>12</deviceSubtypeId>
            <id>355</id>
            <priority>1</priority>
            <projectId>10</projectId>
            <projectName>project Sync Rallydev</projectName>
            <softwareComponentId>266</softwareComponentId>
            <softwareComponentName>vdnt-s</softwareComponentName>
            <testFolderId>20000</testFolderId>
            <testFolderName>Test Folder For Performance</testFolderName>
            <type>CI</type>
         </e>
      </automationRule>
   </automationRuleList>
   <status>OK</status>
</Response>


1. XPath Match Configuration 通过节点判断返回值
declare namespace xmlns='${#Project#host}/TestDirectory/api/v1.0/automationrule';
/xmlns:Response/xmlns:status
OK




<html>
   <head>
      <meta content="HTML Tidy for Java (vers. 27 Sep 2004), see www.w3.org" name="generator"/>
      <title>Apache Tomcat/7.0.32 - Error report</title>
      <style type="text/css">&lt;!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-

family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-

color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-

serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name

{color : black;}HR {color : #525D76;}--></style>
   </head>
   <body>
      <h1>HTTP Status 404 - Not Found</h1>
      <hr noshade="noshade" size="1"/>
      <p>
         <b>type</b>
         Status report
      </p>
      <p>
         <b>message</b>
         <u>Not Found</u>
      </p>
      <p>
         <b>description</b>
         <u>The requested resource is not available.</u>
      </p>
      <hr noshade="noshade" size="1"/>
      <h3>Apache Tomcat/7.0.32</h3>
   </body>
</html>

1. Valid HTTP status codes Assertion判断返态
404



Property transfer: see the screenshot



















  • 大小: 49 KB
  • 大小: 56.7 KB
  • 大小: 75.2 KB
  • 大小: 43.7 KB
  • 大小: 40.4 KB
  • 大小: 40.7 KB
  • 大小: 61.6 KB
分享到:
评论

相关推荐

    Mastering.SoapUI.178398080X

    Design real-time test automation frameworks for Enterprise applications using SoapUI Learn how to solve test automation issues for complex systems A complete guide to understanding SOA automation from...

    soapUI LoadTest

    NULL 博文链接:https://bochuxt.iteye.com/blog/1250706

    webservice test with SOAPUI 详细教程

    webservice test with SOAPUI 详细教程-pro version

    SoapUI 5.4.0-EB

    把一个或多个测试套件(TestSuite)组织成项目,每个测试套件包含一个或多个测试用例(TestCase),每个测试用例包含一个或多个测试步骤,包括发送请求、接受响应、分析结果、改变测试执行流程等

    测试工具

    测试工具用于soapui testtool的externa java工具的存储库将罐子添加到SoapUI 将文件夹“ jars”中的两个jars jxl-2.6.jar和soapuitools.jar复制到SoapUI:s“ ext”文件夹中。 在典型安装中,此文件夹位于“ C:\ ...

    SoapUI-Pro-x64-5.1.2.zip

    把一个或多个测试套件(TestSuite)组织成项目,每个测试套件包含一个或多个测试用例(TestCase),每个测试用例包含一个或多个测试步骤,包括发送请求、接受响应、分析结果、改变测试执行流程等。

    SoapUI-5.3.0.zip

    把一个或多个测试套件(TestSuite)组织成项目,每个测试套件包含一个或多个测试用例(TestCase),每个测试用例包含一个或多个测试步骤,包括发送请求、接受响应、分析结果、改变测试执行流程等。

    SoapUI-5.2.0.rar

    把一个或多个测试套件(TestSuite)组织成项目,每个测试套件包含一个或多个测试用例(TestCase),每个测试用例包含一个或多个测试步骤,包括发送请求、接受响应、分析结果、改变测试执行流程等。

    soapUI-x32-4.5.2.rar

    把一个或多个测试套件(TestSuite)组织成项目,每个测试套件包含一个或多个测试用例(TestCase),每个测试用例包含一个或多个测试步骤,包括发送请求、接受响应、分析结果、改变测试执行流程等。

    SoapUI3.6.0 part3 最新版

    Part of the loadUI Release we are introducing ... Using only drag-and-drop you can do Long-Running Tests, Distributed Load Testing, Run Multiple TestCases Simultaneously and interactive Load Testing.

    Web.Services.Testing.with.soapUI

    and open source tools are avaialble to test web services automatically. soapUI is one such free and open source testing tool that suppots functional and non-functional evaluations of web services.

    SoapUI-x32-5.0.0.rar

    把一个或多个测试套件(TestSuite)组织成项目,每个测试套件包含一个或多个测试用例(TestCase),每个测试用例包含一个或多个测试步骤,包括发送请求、接受响应、分析结果、改变测试执行流程等。

    soapUI测试rest接口操作步骤

    1、使用soapUI对rest接口 进行测试的步骤; 2、主要是用于test/xml消息体的测试

    SoapUI-Pro-x64-5.1.2.exe

    把一个或多个测试套件(TestSuite)组织成项目,每个测试套件包含一个或多个测试用例(TestCase),每个测试用例包含一个或多个测试步骤,包括发送请求、接受响应、分析结果、改变测试执行流程等。 SOAPUl是由标准...

    SoapUI 5.1.2 crack

    Test faster and smarter with data-driven testing, increasing your API testing coverage overnight. LEARN MORE Test Reporting Need metrics, statistics and other testing data? Get detailed, ...

    SOAPUI资料

    soapui入门测试文档,适用于雾测试经验的人群,概念简单,易学,通俗易懂

    接口测试工具-SoapUI

    Soap ui提供一个工具通过soap/http来检查,调用,实现web service和web service的功能/负载/符合性测试....

    soapui-plugin-file-export:SoapUI OS Pro File Utility插件-用于从Project,TestSuite,TestCase和TestStep级别导出请求和响应

    SoapUI OS / Pro插件-用于从Project,TestSuite,TestCase和TestStep级别导出请求和响应。 下载Java归档文件(JAR): 关于插件: ### SoapUI – “导出请求和响应插件”基本上是Java存档文件(JAR),已对其进行...

    soapUI-3.6.1

    把一个或多个测试套件(TestSuite)组织成项目,每个测试套件包含一个或多个测试用例(TestCase),每个测试用例包含一个或多个测试步骤,包括发送请求、接受响应、分析结果、改变测试执行流程等。

    Soapui接口功能测试

    接下来我们按照这个过程详细讲解image.png大家看了图之后对各个对象可能还不太了解,诸如workSpace,project,testSuite,testCase,testStep等,可以看看下面这张图image.png我想这下应该明白了不少吧,别着急,...

Global site tag (gtag.js) - Google Analytics