`

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

    "soapUI LoadTest"是一个关于使用开源自动化测试工具soapUI进行负载测试的主题。soapUI是一款广泛应用于Web服务测试，特别是SOAP（Simple Object Access Protocol）和REST（Representational State Transfer）接口...

    SoapUI-5.4.0.dmg MAC

    6. **负载测试**：利用SoapUI的LoadTest功能，可以模拟多个并发用户对API进行压力测试，评估其性能和稳定性。 7. **安全性测试**：SoapUI包含了WS-Security测试功能，可以帮助识别和修复SOAP服务中的安全漏洞，如...

    soapui的一些资料

    "使用SOAPUI对WEBSERVICE进行性能测试.doc"文档将指导你如何利用SOAPUI的LoadTest功能进行性能测试。你可以模拟多个并发用户，分析响应时间和吞吐量，评估服务在高负载下的稳定性和性能瓶颈。 5. **测试用例设计**...

    SoapUI简易使用手册

    SoapUI是一款广泛应用于接口测试领域的专业工具，尤其在Web服务测试方面表现卓越。它支持SOAP（Simple Object Access Protocol）和REST（Representational State Transfer）两种主流的接口类型，能够进行功能测试、...

    webservice test with SOAPUI 详细教程

    【WebService测试与SOAPUI详解教程】 在IT行业中，测试Web服务接口是确保应用程序质量的关键步骤。SOAPUI是一款广泛使用的工具，专门用于测试基于SOAP（Simple Object Access Protocol）的Web服务。本教程将深入...

    使用SOAPUI对WEBSERVICE进行性能测试.doc

    使用 SOAPUI 对 WEBSERVICE 进行性能测试 SOAPUI 是一个功能强大且广泛应用的性能测试工具，能够对 WEBSERVICE 进行详细的性能测试。在本文中，我们将详细介绍如何使用 SOAPUI 对 WEBSERVICE 进行性能测试，包括...

    SoapUI5+Selenium Webdriver配置

    4. **创建Selenium TestSuite**: 在SoapUI中，新建一个TestSuite，并命名为"Selenium TestSuite"。在这个TestSuite中，我们将创建用于Web界面测试的TestCase。 5. **配置WebDriver Settings**: 在TestSuite级别，...

    SoapUI 5.4.0-EB

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

    soapUI工具使用.rar

    9. **负载测试**：除了基本的功能测试，soapUI还提供了LoadTest功能，用于模拟多个并发用户对服务进行压力测试，评估服务在高负载下的性能和稳定性。 10. **数据源连接**：soapUI可以连接到各种数据源，如数据库、...

    soapUI接口测试指南

    soapUI的LoadTest功能允许模拟大量并发用户，测试接口在高负载下的性能和稳定性。 9. **安全性测试**： soapUI内置了WS-Security测试，可用于检测SOAP服务的安全漏洞。此外，还能进行RESTful服务的身份验证和授权...

    soapui 5.4.0-EB

    4. **负载测试**：SOAPUI的LoadTest功能允许模拟大量并发用户，以评估服务在高负载下的性能和稳定性。 5. **数据源集成**：可以连接到各种数据库、CSV文件或其他数据源，实现动态数据注入，进行真实场景模拟。 6. ...

    soapui开源测试工具

    **SOAPUI开源测试工具详解** SOAPUI是一款强大的开源测试工具，专为Web Service的测试而设计，涵盖了功能测试、负载测试、性能测试和符合性测试等多个方面。它以SOAP（简单对象访问协议）和HTTP为基础，允许用户...

    soapui测试接口工具

    - SOAPUI的LoadTest功能允许你模拟多用户并发请求，评估接口在高负载情况下的性能和稳定性。 5. **数据驱动测试**： - 通过使用数据源（如CSV文件或数据库），SOAPUI可以实现数据驱动测试，用不同的输入数据执行...

    soapUI-4.5.2.zip

    3. **负载测试：** soapUI内置了LoadTest功能，可以模拟多用户并发访问，评估服务在高负载下的性能和稳定性。 4. **数据驱动测试：** 可以使用外部数据源如CSV或Excel文件驱动测试，实现参数化测试，增加测试覆盖率...

    测试工具

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

    soapUI测试介绍

    测试套件(TestSuite)是组织一组紧密相关的测试用例的集合。测试用例(TestCase)通常包括一个或多个请求，用于验证特定的功能点。测试步骤(TestStep)是构成测试用例的各个部分，每个步骤都描述了一个测试用例的某个...

Magicbox
Global site tag (gtag.js) - Google Analytics