CFP: Workshop TESTBEDS 2009: TESTing Techniques & Experimentation Benchmarks for Event-Driven Software
- From: Atif Memon <atif@xxxxxxxxxx>
- Date: Tue, 23 Sep 2008 23:06:16 -0400
Web-site: http://www.cs.umd.edu/~atif/testbeds2009/testbeds2009.htm
Submission deadline: Friday, 9 January, 2009
First International Workshop on TESTing Techniques & Experimentation Benchmarks for Event-Driven Software (TESTBEDS 2009)
Theme for 2009: GUI-Based Applications
Co-located with The IEEE International Conference on Software Testing Verification and Validation (http://bitterroot.vancouver.wsu.edu/icst2009/)
Workshop Overview & Goals: As computers and embedded devices play an increasingly important role aiding end users, researchers, and businesses in today's inter-networked world, several classes of event-driven software (EDS) applications are becoming ubiquitous. Common examples include graphical user interfaces (GUIs), web applications, network protocols, embedded software, software components, and device drivers. An EDS takes internal/external events (e.g., commands, messages) as input (e.g., from users, other applications), changes its state, and sometimes outputs an event sequence. An EDS is typically implemented as a collection of event handlers designed to respond to individual events. Nowadays, EDS is gaining popularity because of the advantages this ``event-handler architecture'' offers to both developers and users. From the developer's point of view, the event handlers may be created and maintained fairly independently; hence, complex system may be built using these loosely coupled pieces of code. In interconnected/distributed systems, event handlers may also be distributed, migrated, and updated independently.
From the user's point of view, EDS offers many degrees of usage freedom. Forexample, in GUIs, users may choose to perform a given task by inputting GUI events (mouse clicks, selections, typing in text-fields) in many different ways in terms of their type, number and execution order.
Quality assurance (QA) is becoming increasingly important for EDS as its correctness may affect the quality of the entire system in which the EDS operates. Software testing is a popular QA technique employed during software development and deployment to help improve its quality. During software testing, test cases are created and executed on the software. One way to test an EDS is to execute each event individually and observe its outcome, thereby testing each event handler in isolation. However, the execution outcome of an event handler may depend on its internal state, the state of other entities (objects, event handlers) and/or the external environment. Its execution may lead to a change in its own state or that of other entities. Moreover, the outcome of an event's execution may vary based on the sequence of preceding events seen thus far. Consequently, in EDS testing, each event needs to be tested in different states. EDS testing therefore may involve generating and executing sequences of events, and checking the correctness of the EDS after each event. Test coverage may not only be evaluated in terms of code, but also in terms of the event-space of the EDS. Regression testing not only requires test selection, but also repairing obsolete test cases. The first major goal of this workshop is to bring together researchers and practitioners to discuss some of these topics.
One of the biggest obstacles to conducting research in the field of EDS testing is the lack of freely available standardized benchmarks containing artifacts (software subjects and their versions, test cases, coverage-adequate test suites, fault matrices, coverage matrices, bug reports, change requests), tools (test-case generators, test-case replayers, fault seeders, regression testers), and processes (how an experimenter may use the tools and artifacts together) [see http://www.cs.umd.edu/~atif/newsite/benchmarks.htm for examples] for experimentation. The second major goal of this workshop is to promote the development of concrete benchmarks for EDS.
To provide focus, the 2009 event will only examine GUI-based applications (no web applications). As this workshop matures, we hope to expand to other types of EDS (e.g., web applications).
Important Dates
Submission of Full Papers: Friday, 9 January, 2009
Notification: Friday, 27 February, 2009
Camera-Ready: Friday, 20 March, 2009
Workshop: April 4, 2009
The workshop solicits submission of:
Full Papers (max 8 pages)
Position Papers (max 4 pages)
Demo Papers (max 4 pages)
Industrial Presentations (slides)
All submissions will be handled through the ICST 2009 submission web-site (http://bitterroot.vancouver.wsu.edu/icst2009/index.html).
Industrial presentations are submitted in the form of presentation slides and will be evaluated by at least two members of the Program Committee for relevance and soundness.
Each paper will be reviewed by at least three referees. Papers should be submitted as PDF files in standard IEEE two-column conference format (Latex ftp://pubftp.computer.org/Press/Outgoing/proceedings/IEEE_CS_Latex.zip, Word ftp://pubftp.computer.org/Press/Outgoing/proceedings/FORMAT.DOC). The workshop proceedings will be published on the workshop web-page. Papers accepted for the workshop will appear in the IEEE digital library, providing a lasting archived record of the workshop proceedings.
General Chair
Atif M Memon, University of Maryland, USA.
Program Committee
Fevzi Belli, University of Paderborn, Germany.
Renee Bryce, Utah State University, USA.
S.C. Cheung, The Hong Kong University of Science and Technology, Hong Kong.
Myra Cohen, University of Nebraska Lincoln, USA.
Chin-Yu Huang, National Tsing Hua University, Taiwan.
Scott McMaster, Amazon.com, USA.
Brian P Robinson, ABB Corporate Research, USA.
Qing Xie, Accenture Technology Labs, Chicago, USA.
Xun Yuan, Google, USA.
.
- Prev by Date: ISEB Foundation Level Certification
- Next by Date: ONSITE-Embedded Testing with QNX- for TOP MNC-CMM Level Company
- Previous by thread: ISEB Foundation Level Certification
- Next by thread: ONSITE-Embedded Testing with QNX- for TOP MNC-CMM Level Company
- Index(es):
Relevant Pages
|
