Co-located with The IEEE
International Conference on Software Testing Verification and Validation
Please look at http://guitar.sourceforge.net for more
work on automated GUI testing.
Second
International Workshop on
TESTing
Techniques & Experimentation Benchmarks
for Event-Driven
Software
(TESTBEDS 2010)
Theme for 2010: GUI-Based Applications and Rich Internet
Applications
09:00
- 09:30
|
Opening Remarks |
09:30
- 10:30
|
Keynote
Dr. Peter Santhanam, Senior Manager, Software Engineering, IBM T. J. Watson Research Center. Abstract Biography: |
10:30
- 11:00
|
Coffee Break
|
11:00
- 12:30
|
Session 1
|
12:30
- 14:00
|
Lunch
|
14:00
- 15:30
|
Session 2
|
15:30
- 16:00
|
Closing Remarks and
Coffee
|
With the
tremendous success of TESTBEDS 2009,
we are happy to announce this second workshop. As the participants of TESTBEDS 2009
noted in several interesting talks and discussions, testing of several classes
of event-driven software (EDS)
applications is becoming very important. Common examples of EDS 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. For example, 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.
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, this event will only examine GUI-based applications and Rich Internet
Applications, which share many testing challenges. As this workshop matures, we
hope to expand to other types of EDS (e.g., general web applications).
The
workshop solicits submission of:
·
Full
Papers (max 10 pages)
·
Position
Papers (max 4 pages) [what
is a position paper?]
·
Demo
Papers (max 4 pages) [usually papers describing implementation-level details
(e.g., tool, file format, structure) that are of interest to the community]
·
Industrial
Presentations (slides)
All submissions will be handled
through http://www.easychair.org/conferences/?conf=testbeds2010.
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
, Word).
The workshop proceedings will be published on this workshop web-page. Papers
accepted for the workshop will appear in the IEEE digital library, providing a
lasting archived record of the workshop proceedings.
·
Atif M Memon, University of Maryland, USA.
·
Fevzi
Belli, University of Paderborn, Germany.
·
Renee Bryce, Utah State
University, USA.
·
Kai-Yuan
Cai, Beijing University
of Aeronautics and Astronautics, China.
·
S.C. Cheung, Hong Kong University of
Science and Technology, Hong Kong.
·
Myra Cohen, University of Nebraska –
Lincoln, USA.
·
Anna
Rita Fasolino, University of Naples Federico II,
Italy.
·
Chin-Yu Huang, National Tsing Hua University, Taiwan.
·
Alessandro
Marchetto, Fondazione
Bruno Kessler–IRST, Trento, Italy.
·
Ana Paiva,
University of Porto, Portugal.
·
Brian
P Robinson, ABB Corporate Research, USA.
·
Qing
Xie, Accenture Technology Labs, Chicago, USA.