60 likes | 198 Vues
This document outlines a structured approach to scripting test cases and mapping test event logs (TEL) to external actions. It describes a reusable test flow that operates continuously for specific event types, ensuring robust integration within test cases of a suite. Key components include an adapter for web services, event checks, logging mechanisms, and recovery procedures post-testbed system failures. The framework emphasizes resilience, efficiency, and systematic event data management, essential for quality assurance in software testing.
E N D
Test Case Scripting: Requirements and Design Sketches • Jacques Durand • with additions from Jaewook Kim
TEL (Test Event Log) Mapping Test Case Events to External Actions A testflow continuously running (loop) for mapping events of a certain type to external actions. (reusable across all Test Cases of a test suite.) Main testflow of The Test Case Put-event Get-event Get-event Map-event adapter Web Service or ebXML Message Check & Brch MSH or WS stack Branch Exit(fail) adapter Exit(pass) Manual Put-event for Output Mapping Test
TEL Check-and-log Check-and-log Put-event Get-event Put-event Get-event Check-and-exit Check-and-exit
Test Recovery TEL after testbed system recovery testbed system shutdown Put-event Get-event Put-event Get-event Check-and-exit Check-and-exit
Put-event Action ebXML Message Web Service Message Put-event MSH Manual Put-event for Output Mapping Test MSH Engineer
Recovery and State Persistence Event data (message data) State data Put-event TEL Get-event Check & Brch Exit(fail) Exit(pass) Event log State logs (1 for each test case execution)