Although developers have been unit testing their code for years, it was typically performed after the code was designed and written. As a great number of developers can attest, writing tests after the fact is difficult to do and often gets omitted when time runs out.

Test-driven development (TDD) attempts to resolve this problem and produce higher quality, well-tested code by putting the cart before the horse and writing the tests before we write the code. One of the core practices of Extreme Programming (XP), TDD is acquiring a strong following in the Java community,

 but very little has been written about doing it in .NET.

Test-Driven Development In .NET

Website from the books eXtreme Programming Explored/Installed/... ,
contains lots of information about processes, refactoring, ...

http://www.xp123.com/xplor/
-----------------------------------------------------
Mail.be, WebMail and Virtual Office
http://www.mail.be

Read all about it at:

   <http://www.mcbreen.ab.ca/papers/WhenEstimateIsWrong.html>

From the summary:

   This paper examines the challenges of testing enterprise
integration solutions and proposed a testing approach to tackle the
inherent complexities. This approach is accompanied by a framework
that makes integration testing more effective and efficient.

   Additionally, the paper discusses the implications of Web services
and service-oriented architectures on the proposed testing framework,
and provides guidelines for the design of new integration solutions
to improve testability.

   <http://www.hohpe.com/Gregor/Work/docs/TestDrivenEAI.pdf>

ABSTRACT

   In this paper we describe techniques that we have found helpful for
adding unit tests to existing code that has been written without
tests. The paper presents some common coding practices that make unit
tests hard to retrofit, and why. For each practice we suggest minimal
refactorings to open up the code for testing.

   <http://www.cwi.nl/events/2002/wtixp/papers/Freeman.pdf>

Perhaps bad and nonexistent documentation is to be expected. Ever seen good code
comments in a book? Ever heard a programmer being praised for well commented
code? The best you can hope for is a smattering of mind-numblingly dull and
ridiculously incomplete Word documents that are a year or more out of date.

We are used to the culture of making others dig thru the dirt. It is considered
a badge of honor to decipher how a piece of code works and should be used.

Read more on http://www.artima.com/weblogs/viewpost.jsp?thread=4183
-----------------------------------------------------
Mail.be, WebMail and Virtual Office
http://www.mail.be

According to a poll on Embedded.com, 68% of the respondents are using C for developing their embedded software. Why do embedded developers choose C over C++? Sure, there are some practical reasons to avoid C++, such as the availability of tools for your embedded processor. But another possibility is that embedded programmers do not know the advantages that an Object Oriented programming language can bring them. They may not know what the tradeoffs are when choosing to use C++ over C. This article describes some of the key reasons to use the OO features of C++ in your embedded applications and how to evaluate the cost tradeoffs.

More in this in: Why Are You Still Using C ?

Hello everybody,
as a part of the NAME (Network for Agile Methodologies Experience)
project we have prepared a research roadmap on agile methodologies.

You can read the roadmap in pdf format at
<http://name.case.unibz.it/NameResearchRoadmap-v2/NAMERoadmapVf.pdf>

and as a navigable mind diagram at
<http://name.case.unibz.it/NameResearchRoadmap-v2/index.html>

Comments are welcome and can also be mailed to NAME@...

Regards

Manlio

OpenSTA is a distributed testing architecture that enables you to create and run
performance Tests to evaluate Web Application Environments (WAEs) and production
systems. It can be employed at all stages of WAE development as well as being
used to continuously monitor system performance once a WAE goes live.

Use it to develop load Tests that include an HTTP/S load element, known as
Scripts, to help assess the performance of WAEs during development, and to
create Collector-only Tests that monitor and record performance data from live
WAEs within a production environment.

OpenSTA enables you to run Tests against the same target system within both load
testing and production monitoring scenarios. This means that you can directly
compare the performance of the target system within these two environments.

www.opensta.org
___________________________________________________

  The Proxy Sniffer v2.9 tool contains a unique, special proxy server with
integrated ssl tunnels to record unencrypted as well as encrypted HTTP(S) web
browser surf sessions. It generates - based on these recorded surf sessions -
automatically load test programs in form of Java source code, which can be
executed from any system that supports Java. By using a multi-processor UNIX
server as load source its possible to emulate up to 500 parallel web surf
sessions from one node. The product has also a build-in web server which allows
a graphical analysis of the measured test results.

http://www.proxy-sniffer.com/index_en.html

__________________________________________________

What is The Grinder?

The Grinder is a Java™ load-testing framework. It is freely available under a
BSD-style open-source license.

The Grinder makes it easy to orchestrate the activities of a test script in many
processes across many machines, using a graphical console application. Test
scripts make use of client code embodied in Java plug-ins. Most users of The
Grinder do not write plug-ins themselves, instead they use one of the supplied
plug-ins. The Grinder comes with a mature plug-in for testing HTTP services, as
well as a tool which allows HTTP scripts to be automatically recorded.

The Grinder was originally developed for the book Professional Java 2 Enterprise
Edition with BEA WebLogic Server by Paco Gómez and Peter Zadrozny. Philip Aston
took ownership of the code and reworked it to create The Grinder 2. Philip
continues to enhance and maintain The Grinder, and welcomes all contributions.
Recently Peter, Philip and Ted Osborne have published the book J2EE Performance
Testing which makes extensive use of The Grinder.

_____________________________________________

TestMaker (formerly Load) is a framework for building intelligent test agents to
check Web Services for scalability, performance and functionality.

http://www.pushtotest.com/ptt/downloads.html
-----------------------------------------------------
Mail.be, WebMail and Virtual Office
http://www.mail.be

Malcolm Groves explains how to get started using DUnit.

   <http://www.adug.org.au/meetings/Symposia/2002/UnitTestingView.pdf>

Dave Thomas and Andy Hunt explain how State Machines can simplify many of our programs.

In The Art of Enbugging Dave and Andy teach us how proper separation of concerns keeps bugs out of the code.

Hi All

Anyone interested may join at
http://groups.yahoo.com/group/ExtremeProgrammingNewDelhi/


Bye

Yahayolo

The industry speaks positively about agile methods for software development (http://www.agilealliance.org) but hasn't yet applied those principles to the folks who do networking and infrastructure. It is overdue and I will take the first shot at some things that can make them more agile:

James McGovern
Co-author of the book: Java Web Services Architecture http://www.amazon.com/exec/obidos/ASIN/1558609008/chiltownworldwid/

and co-author of the upcoming book: The Practical Guide to Enterprise Architecture

----- Original Message -----

From: philippe tseyen

To: agilearticles@yahoogroups.com

Sent: Monday, May 12, 2003 1:19 PM

Subject: [agilearticles] XML Unit

I was browsing the web while I found XML Unit.

I haven't tried it myself (yet), but it looks promising.

---

Post your free ad now! Yahoo! Canada Personals


To unsubscribe from this group, send an email to:
agilearticles-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Fowler recently added this list of database refactorings to his site.

   <http://martinfowler.com/dbrefact/>

Rebecca Parsons talks about: Components and the World of Chaos

The Pragmatic Programmers contrast the risks of overcomplicating to those of oversimplifying in their latest article: The Trip-Packaging Dilemma

Robert Martin states it clearly: We will not ship shit

Added the link to Agile Alliance Europe Website to the bookmark section

Kind Regards,
Sven

Ran across this last night while on Eric Raymond's blog.  Doesn't look
like it's been posted here before ...

http://armedndangerous.blogspot.com/2003_06_08_armedndangerous_archive.html#1055\
63829929887753

(ESR is a well-known open-source personality and author of The
Cathedral and the Bazaar, a "history of hacker culture".)

Mike Colbert

Book Review: Extreme Programming Refactored

Ron Jeffries:
   This book is painful to read for anyone who understands what XP is,
because the authors have gone to such pains not to understand, to
take out of context, and to distort.

   It is dangerous to read for anyone who does not understand what XP
is, because the authors have gone to such pains not to understand, to
take out of context, and to distort.

Read more at:
   <http://www.xprogramming.com/xpmag/books20030904.htm>

Martin Fowler on the dubious role of "software architect":

"For many, the term 'software architect' fits perfectly with the smug
controlling image at the end of Matrix Reloaded."

<http://www.martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf>