[Webtest] Fwd: Call for Participation: Functional Testing Tools Visioning Workshop
Lisa Crispin
Lisa Crispin" <lisa.crispin@gmail.com
Thu, 26 Jul 2007 11:06:53 -0600
------=_Part_173473_2656300.1185469613407
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
It would be great if someone from the WebTest community could attend this.
I'm attending PNSQC in Portland Oct. 8 - 10, but I'm not sure I can stay fo=
r
this. If anyone is interested, please let me know as well as responding pe=
r
the instructions below.
thanks
Lisa
*Agile Alliance Functional Testing Tools Visioning Workshop*
*Call for Participation *
Dates: October 11 - 12, 2007
Times: 8 AM - 5 PM
Location: Portland, Oregon
Venue: Kennedy School
*Description*
The primary purpose of this workshop is to discuss cutting-edge advancement=
s
in and envision possibilities for the future of automated functional testin=
g
tools.
This is a small, peer-driven, invitation-only conference in the tradition o=
f
LAWST, AWTA, and the like. The content comes from the participants, and we
expect all participants to take an active role. We're seeking participants
who have interest and experience in creating and/or using automated
functional testing tools/frameworks on Agile projects.
This workshop is sponsored by the Agile Alliance Functional Testing Tools
Program. The mission of this program is to advance the state of the art of
automated functional testing tools used by Agile teams to automate
customer-facing tests.
There is no cost to participate. Participants will be responsible for thei=
r
own travel expenses. (However, we do have limited grant money available to
be used at the discretion of the organizers to subsidize travel expenses.
If you would like to be considered for a travel grant, please include your
request, including amount needed, in your Request for Invitation.)
*Requesting an Invitation*
If you're interested in being invited to participate in this workshop,
please send an email to " testtoolworkshop@agilealliance.org" answering the
following questions:
1. What is your experience using functional tests as a way to specify
functional requirements?
2. What is your experience with automated functional testing tools on Agile
projects?
3. What do you hope to contribute to the workshop? Do you have any code or
examples that you'd like to share? (Please note that you should not share
anything covered by a non-disclosure agreement.)
4. What do you hope to get out of the workshop?
Invitations will be issued by September 1, 2007 so that we can confirm hote=
l
room requirements. *Please send in your request as soon as possible, befor=
e
the workshop fills up.*
*Pass This Along*
If you know of someone that would be a candidate for this workshop, please
forward this call for participation on to them.
**
*Additional Background*
Automated functional testing is an integral and essential part of Agile
development. Many Agile teams use functional tests to codify the system
requirements. Some also practice Acceptance Test Driven Development.
Agile teams have particular needs for automated tools that are not well
served by traditional record-and-playback GUI drivers. As requirements
specifications, functional tests must be readable: clear, succinct, and
expressed in the language of the business domain. As an automated safety
net, the tests must be maintainable: built with reusable domain specific
testing language components, easy to change as the requirements change.
The good news is that tool support for automated functional tests has grow=
n
significantly in recent years. There is a large variety of commercial and
open source testing tools/frameworks available that support Agile
development practices. The FIT framework was a significant boost to the
state of the art of automated functional testing, both in terms of the
syntax of the specification (tables), the detailed test execution feedback
(cell by cell), and the development/execution environment (desktop tools
rather than development or specialized tools).
However, we believe that it's time for another significant boost to the
state of the art.
- We are lacking integrated development environments that facilitate things
like: refactoring test elements, command completion, incremental syntax
validation (based on the domain specific test language), keyboard navigatio=
n
into the supporting framework code, debugging, etc.
- We need more expressive test specification languages, possibly integratin=
g
executable: text, tables, shapes, and colors together into a single test.
- We need specification languages that can describe user interaction in a
readable and maintainable fashion.
- We need to be able to view/navigate the tests in multiple different ways
in order to see how the pieces of the puzzle contribute to the bigger
picture of the domain/feature: organize tests based on their domain context=
;
search for tests based on user-defined keywords (cross cutting concerns).
- =85 and things that we haven't even thought of that will take us out of t=
he
current box, and into a new level of effectiveness =85.
The Agile Alliance Functional Testing Tools Program seeks to advance the
state of the art by creating opportunities for people who are in a position
to advance the state of the art to share information and ideas, and explore
possibilities.
--=20
Lisa Crispin
Co-author,
Testing Extreme Programming
http://lisa.crispin.home.att.net
------=_Part_173473_2656300.1185469613407
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
It would be great if someone from the WebTest community could attend this.&=
nbsp; I'm attending PNSQC in Portland Oct. 8 - 10, but I'm not sure=
I can stay for this. If anyone is interested, please let me know as =
well as responding per the instructions below. =20
<br>thanks<br>Lisa<br><br><span class=3D"gmail_quote"><br></span><div><b>Ag=
ile Alliance Functional Testing Tools Visioning Workshop</b></div>
<div><b>Call for Participation </b></div><span>
<div><font color=3D"#000000">Dates: October 11=
- 12, 2007</font></div>
<div>Times: 8 AM - 5 PM</div>
<div><font color=3D"#000000">Location: Portland, Oregon </font></div></span=
>
<div><font color=3D"#000000">Venue: Kennedy School</font>=
</div>
<div><span><br><b><font color=3D"#000000">Description</font></b></span></di=
v>
<div><span lang=3D"EN-CA"><font color=3D"#000000">The primary purpose of th=
is workshop is to discuss cutting-edge advancements in and envision possibi=
lities for the future of automated functional testing tools.</font></span>
</div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">This is a small, peer-driven, invitation-only =
conference in the tradition of LAWST, AWTA, and the like. The content comes=
from the participants, and we expect all participants to take an active ro=
le. We're seeking participants who have interest and experience in crea=
ting and/or using automated functional testing tools/frameworks on Agile pr=
ojects.=20
</font></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">This workshop is sponsored by the Agile Allian=
ce Functional Testing Tools Program. The mission of this program=
is to advance the state of the art of automated functional testing tools u=
sed by Agile teams to automate customer-facing tests.=20
</font></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">There is no cost to participate. Pa=
rticipants will be responsible for their own travel expenses. (Howeve=
r, we do have limited grant money available to be used at the discretion of=
the organizers to subsidize travel expenses. If you would like to be=
considered for a travel grant, please include your request, including amou=
nt needed, in your Request for Invitation.)=20
</font></div><span>
<div><br><b><font color=3D"#000000">Requesting an Invitation</font></b></di=
v>
<div><font color=3D"#000000">If you're interested in being invited to p=
articipate in this workshop, please send an email to "</font><a href=
=3D"mailto:testtoolworkshop@agilealliance.org" target=3D"_blank" onclick=3D=
"return top.js.OpenExtLink(window,event,this)">
<font color=3D"#000000">testtoolworkshop@agilealliance.org</font></a><font=
color=3D"#000000">" answering the following questions:</font></d=
iv>
<div><font color=3D"#000000"> </font></div></span>
<div><font color=3D"#000000">1. What is your experience using functional te=
sts as a way to specify functional requirements? <br> </font></div><sp=
an>
<div><font color=3D"#000000">2. What is your experience with automated func=
tional testing tools on Agile projects? </font></div>
<div><font color=3D"#000000"> </font></div></span><span>
<div><font color=3D"#000000">3. What do you hope to contribute to the works=
hop? Do you have any code or examples that you'd like to share? (Please=
note that you should not share anything covered by a non-disclosure agreem=
ent.)=20
</font></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">4. What do you hope to get out of the workshop=
?</font></div>
<div><font color=3D"#000000"> </font></div></span>
<div><font color=3D"#000000">Invitations will be issued by September 1, 200=
7 so that we can confirm hotel room requirements. <u>Please send=
in your request as soon as possible, before the workshop fills up.</u></fo=
nt></div>
<span>
<div><br><b><font color=3D"#000000"><strong>Pass This Along</strong></font>=
</b></div>
<div>If you know of someone that would be a candidate for this workshop, pl=
ease forward this call for participation on to them.</div>
<div><strong></strong> </div>
<div><b><font color=3D"#000000">Additional Background</font></b></div>
<div><span lang=3D"EN-CA"><font color=3D"#000000">Automated functional test=
ing is an integral and essential part of Agile development. Many Agil=
e teams use functional tests to codify the system requirements.<span> =
Some also practice Acceptance Test Driven Development.=20
</span></font></span></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">Agile teams have particular needs for automate=
d tools that are not well served by traditional record-and-playback GUI dri=
vers. <span lang=3D"EN-CA">As requirements specifications, funct=
ional tests must be readable: clear, succinct, and expressed in the languag=
e of the business domain.=20
<span> </span>As an automated safety net, the tests must be main=
tainable: built with reusable domain specific testing language components, =
easy to change as the requirements change.</span></font></div>
<div><br><font color=3D"#000000"> </font><span lang=3D"EN-CA"><span la=
ng=3D"EN-CA"><font color=3D"#000000">The good news is that tool support for=
automated functional tests has grown significantly in recent years.<span>&=
nbsp; </span>
There is a large variety of commercial and open source testing tools/framew=
orks available that support Agile development practices. <span> </spa=
n>The FIT framework was a significant boost to the state of the art of auto=
mated functional testing, both in terms of the syntax of the specification =
(tables), the detailed test execution feedback (cell by cell), and the deve=
lopment/execution environment (desktop tools rather than development or spe=
cialized tools).=20
</font></span></span></div>
<div><span lang=3D"EN-CA"><font color=3D"#000000"> </font></span></div=
>
<div><span lang=3D"EN-CA"><font color=3D"#000000">However, we believe that =
it's time for another significant boost to the state of the art.</font>=
</span></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">- We are lacking integrated development enviro=
nments that facilitate things like: refactoring test elements, command comp=
letion, incremental syntax validation (based on the domain specific test la=
nguage), keyboard navigation into the supporting framework code, debugging,=
etc. =20
</font></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">- We need more expressive test specification l=
anguages, possibly integrating executable: text, tables, shapes, and colors=
together into a single test.</font></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">- We need specification languages that can des=
cribe user interaction in a readable and maintainable fashion.</font></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">- We need to be able to view/navigate the test=
s in multiple different ways in order to see how the pieces of the puzzle c=
ontribute to the bigger picture of the domain/feature: organize tests based=
on their domain context; search for tests based on user-defined keywords (=
cross cutting concerns).=20
</font></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">- =85 and things that we haven't even thou=
ght of that will take us out of the current box, and into a new level of ef=
fectiveness =85.</font></div>
<div><font color=3D"#000000"> </font></div>
<div><font color=3D"#000000">The Agile Alliance Functional Testing Tools Pr=
ogram seeks to advance the state of the art by creating opportunities for p=
eople who are in a position to advance the state of the art to share inform=
ation and ideas, and explore possibilities.=20
</font></div></span>
<br clear=3D"all"><br>-- <br>Lisa Crispin<br>Co-author, <br>Testing Extreme=
Programming<br><a href=3D"http://lisa.crispin.home.att.net">http://lisa.cr=
ispin.home.att.net</a>
------=_Part_173473_2656300.1185469613407--