Leveraging Semantic Web Service Descriptions for Validation by Automated Functional Testing
ESWC 2009 Heraklion Proceedings of the 6th European Semantic Web Conference on The Semantic Web: Research and Applications
OPENET: Ontology-based engine for high-level Petri nets
Expert Systems with Applications: An International Journal
A Framework for Testing Semantic Web Services Using Model Checking
SEEFM '09 Proceedings of the 2009 Fourth South-East European Workshop on Formal Methods
A comparative evaluation of state-of-the-art web service composition testing approaches
Proceedings of the 6th International Workshop on Automation of Software Test
Service research challenges and solutions for the future internet
OCL-based testing for e-learning web service
ICWL'10 Proceedings of the 2010 international conference on New horizons in web-based learning
Using ontology to generate test cases for GUI testing
International Journal of Computer Applications in Technology
Systematic scenario test case generation for nuclear safety systems
Information and Software Technology
A systematic review on the functional testing of semantic web services
Journal of Systems and Software
Data flow analysis and testing for OWL-S semantic web service compositions
International Journal of Computational Science and Engineering
| Hi-index | 0.00 |
Web Services (WS) enables agile application development by orchestrating the existing service components. However, the dynamically constructed service-based system has to be tested dynamically and automatically at runtime without human intervention. To address the challenges of automatic WS test case generation, this paper proposes a model driven ontology-based approach with the purpose of improving test formalism and test intelligence. The semantic WS specification OWL-S is used to describe the application logic of composite service process. A Petri-Net model is created to provide a formal representation of the OWL-S (Web Ontology Language for Web Service) process model. The Petri-Net ontology is defined to incorporate the operation and IOPE (Inputs, Outputs, Preconditions, and Effects) semantics for test generation. Test cases are generated from two aspects. Test steps are generated by traversing various execution paths of the Petri-Net graph. Test data are generated by reasoning over the IOPE ontology.