1 / 15

eBusiness Test Framework Evolution: Challenges and Vision

Explore the evolution of eBusiness testing technology, challenges in maintaining interoperability, and the vision for effective testing frameworks and services in the eBusiness and eGovernment domains. The importance of test centers, conformance testing, and the role of NIST in developing the ebXML testing framework are discussed. Downloadable demos and implementation details are included.

abel-casey
Download Presentation

eBusiness Test Framework Evolution: Challenges and Vision

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IIC Test Framework :illustrated on ebXML Conformance Testing Michael Kass michael.kass@nist.gov Han Kim Ngo hankim.ngo@nist.gov Jacques Durand jdurand@us.fujitsu.com

  2. The IIC [ebXML] Test Framework • V1.0 May 2003, V1.1 October 2004 • An architecture that defines Test Components that work together • Test Driver • Test Service • XML schemas for defining Test Suites • Test Requirements • executable Test Suites (set of Test Cases)

  3. Challenges eBusiness / eGov Testing: • Interoperability needs to be Maintained between Business Partners • Threatened by continuous, non synchronized systems upgrades • eBusiness Interoperability is an integration problem: has to be tested “live”, in production upgrading

  4. Vision for eBusiness / eGov Testing: • The Role of Test Centers • Provide testing services at all phases of eBusiness product life cycle • Early conformance tests • Pre-release Interop tests • Business guidelines tests (vertical) • Interop Maintenance testing

  5. Testing for the “Interoperability Stack” Application Content Interoperability (A2A) • System in Production Conformance to Business Guidelines Protocol-level Interoperability Infrastructure Conformance to Technical Specifications

  6. Vision for eBusiness / eGov Testing: • Testing Technology evolving toward: • Automation and [XML] scripting • Versatile frameworks • various formats/standards, • evolve with them, • ease of customization • Support for Testing will become a product feature, not just a QA thing

  7. Test Framework: Implementations • NIST (US) • Test Driver & Test Service. Intended for local testing. 1.1 Available for beta-testing end of year. • KorBIT (Korea) • 1.0 Test Driver & Test Service. Used remotely at ETSI test event 2004 (ebMS 2.0). • DrakeCertivo (US) • Test Driver. Used for ebMS conformance , and also OAG BODs testing • KWareSoft (Korea)

  8. ebXML Message Handler Test target Test Framework component Testing ebXML MS Conformance Test suite Test Service ebXML Message Test Driver Host 2 Conformance/ Interoperability report Host 1 (or test center)

  9. Test suite Test Service Test Driver ebXML Message Handler ebXML Message Handler Test Service ebXML Message (HTTP / SMTP) Test target Test Framework component Testing MS Interoperability: point-to-point Host 2 Host 1

  10. NIST’s Role • Provide expertise in conformance testing to OASIS IIC • Help develop the OASIS IIC ebXML Testing Framework specification for all ebXML specifications • Prototype a Test Framework implementation as proof of concept • Assist in writing conformance tests for Messaging, Registry, and Business Process specifications

  11. Design Goals • Flexible testing architecture • Provide simple XML scripting • Promote test suite re-use

  12. Test Suite • Testing Requirements • Executable Test Cases • Testing Profile • Associated Message Content

  13. Conformance Test Requirements • Reference Conformance Clause in Specification • Reference the Normative Specification • Broken down into concise Functional (Semantic) Requirements expressed as a Test Assertion Clause “For conformance to this specification, all the version attributes of any SOAP extension elements defined in this specification MUST have a value of “2.0”

  14. Demo ebXML Messaging Services 2.0 Conformance Test Suite Message Packaging - # 2 ebXML Message is in root part of MIME Envelope - #28 MessageHeader version attribute is ‘2.0’

  15. Download • NIST Test Framework Implementation free for download in December at http://ebxmltesting.nist.gov • NIST Test Driver and Test Service (source/binary) • OASIS IIC ebXML MS 2.0 Conformance Test Suite • NIST ebXML RS 2.1 Conformance Test Suite

More Related