DICOM Application Hosting Testing: Difference between revisions

From Commontk
Jump to navigationJump to search
No edit summary
Line 1: Line 1:
==== High - level test suites ====
=== High - level test suites ===


That's what I can see so far:
That's what I can see so far:
Line 6: Line 6:
* Functional testing: Test the "logic" of the host and app (proper state transitions, correct notification messages, etc.)
* Functional testing: Test the "logic" of the host and app (proper state transitions, correct notification messages, etc.)


==== Possible solutions ====
=== Possible solutions ===


Use [http://www.soapui.org/ SoapUI] and its command line support to integrate it with ctest. Automatically generate tests for WSDL compliance using the official WSDL file
* Use [http://www.soapui.org/ SoapUI] and its command line support to integrate it with ctest.
* Create manual functional tests within the SoapUI GUI and put the project file in the CTK git repository
** Automatically generate tests for WSDL compliance using the official WSDL file
** Create manual functional tests within the SoapUI GUI and put the project file in the CTK git repository


==== Requires ====
==== SoapUI ====
 
'''Requires'''


* Either host the SoapUI executable somewhere or look for it if testing is enabled
* Either host the SoapUI executable somewhere or look for it if testing is enabled
Line 17: Line 20:
* Some CMake magic
* Some CMake magic


==== Pros ====
'''Pros'''


* Rely on proven Java libraries to generate the RPC stuff and mock classes for server and client code from the WSDL file.
* Rely on proven Java libraries to generate the RPC stuff and mock classes for server and client code from the WSDL file.
* No C++ involved, create test cases in the GUI
* No C++ involved, create test cases in the GUI
* No programming knowledge required to add or modify tests
* No programming knowledge required to add or modify tests

Revision as of 07:22, 14 November 2011

Home < DICOM Application Hosting Testing

High - level test suites

That's what I can see so far:

  • WSDL compliance: Test if the host and app accept the official method signatures
  • Functional testing: Test the "logic" of the host and app (proper state transitions, correct notification messages, etc.)

Possible solutions

  • Use SoapUI and its command line support to integrate it with ctest.
    • Automatically generate tests for WSDL compliance using the official WSDL file
    • Create manual functional tests within the SoapUI GUI and put the project file in the CTK git repository

SoapUI

Requires

  • Either host the SoapUI executable somewhere or look for it if testing is enabled
  • Java Runtime on the test system
  • Some CMake magic

Pros

  • Rely on proven Java libraries to generate the RPC stuff and mock classes for server and client code from the WSDL file.
  • No C++ involved, create test cases in the GUI
  • No programming knowledge required to add or modify tests