Scribd
Upload
178 views10 pages

QSEE Test Workbench Standardization Proposal

This document proposes standardizing the PLAVIS test environment using XML. It demonstrates this by describing a LabVIEW-based testing tool called the QSEE Test Workbench. The Workbench allows defining test cases and executing black-box tests on embedded software communication protocols. It captures test logs, generates reports, and supports test case reuse. The document suggests integrating the Workbench with an XML test case repository and automatic test generator to improve the testing process. Future work includes enhancing the tool's protocol definition, test parallelism, and user interface.

Uploaded by

silvawp
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
178 views10 pages

QSEE Test Workbench Standardization Proposal

This document proposes standardizing the PLAVIS test environment using XML. It demonstrates this by describing a LabVIEW-based testing tool called the QSEE Test Workbench. The Workbench allows defining test cases and executing black-box tests on embedded software communication protocols. It captures test logs, generates reports, and supports test case reuse. The document suggests integrating the Workbench with an XML test case repository and automatic test generator to improve the testing process. Future work includes enhancing the tool's protocol definition, test parallelism, and user interface.

Uploaded by

silvawp
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd

Proposal of a standardization

for PLAVIS using XML:


a demonstration in LabVIEW

Wendell Pereira da Silva


wendell@[Link]

Advisors

Maria de Fátima Matiello


Valdivino A. de Santiago Jr.
Topics
 QSEE Test Workbench
 Main Features
 Architecture Overview
 Demonstrations
 Proposal of an Integrated Architecture in
PLAVIS’ Domain
 Added Values
 Final Considerations & Future Works

Nov, 03 - 2005
QSEE Test Workbench
 Definition
 A prototype of a desktop application that aids the tester to generate and
execute the tests
 Part of a test environment
 What is it used for?
 Test case implementation
 Test case execution
 Viewing test execution logs and reports
 Black-box testing support (functional testing)
 What is it not?
 Automatic test case generator
 Does it have a specific domain?
 Yes: embedded software
 In theory, it addresses the testing of computer protocols for embedded
software
 OBDH-EXP communication protocol, for instance.

Nov, 03 - 2005
QSEE Test Workbench
Features
 Test project configuration
 Create Test Projects
 IUT Identification, Tester Identification, test cycle definition
 Communication channels setup
 Test cases manager
 Add, remove, edit and organize test cases
 Add, remove, edit and organize test steps
 External observation point capture
 Send/Receive messages (embedded comm. protocol emulation)
 Message template library
 Flexible protocol message edition

Nov, 03 - 2005
QSEE Test Workbench
Features (cont…)
 Running test project
 Test execution logging (per test cycle)
 Automatic verdict assumption
 Allows for conformance test execution
 Allows for fault injection execution
 Test report generation (XML/XSLT)

Nov, 03 - 2005
QSEE Test Workbench
Architecture
 Desktop Application

User Interface Action Workbench


Listeners Controller

sender

Data Structure Manager


receiver

logger
Binary data files
<<test project>>
LabVIEW internal format
Nov, 03 - 2005
Demonstration

Nov, 03 - 2005
Architectural Proposal
CONDADO QSEE - Selector Test Cases

XSL
xml xml
<<XML>>
test sequence Selector
Engine
QSEE Test
Workbench
MGASET

Automatic test data and Test


test case generation SGBD (PLAVIS) Reports

Tester
Nov, 03 - 2005
Added Values
 Planning test cases once and run them easily
 Testing task is self-documented
 Time reduction between test cycles
 More productivity in test execution
 Less testing error prone

Nov, 03 - 2005
Final Considerations & Future
Works
 QSEE Test Workbench still needs:
 To be integrated with automatic test case generators
 To offer a better protocol definition (message format
edition)
 To implement a multi-channel communication
 To implement more types of communication channels
 To capture observation point in parallel with
sending/receiving messages to/from IUT
 To offer a better user interface (more user friendly)

Nov, 03 - 2005

You might also like