comp.software.extreme-programming Google Group

Software Configuration Management: Continuous Integration Widely Adopted

2009-11-24T20:54:30Z

A recent Methods & Tools poll tried to evaluate how software
configuration management (change management / version control) is
performed by organisations. Is it an informal activity or performed
with formal procedures that are validated by an automated tool?
Read the results on [link]

Re: Extending pair programming to groups

2009-11-20T20:22:24Z

The goal is high-quality, realtime communication & decision making.
Pairs rotate frequently, so everyone learn to work with all the modules. And
pairs should work on "pairstations", with dual keyboards & mice. The
pairstations should be in a common programming room, so people can overhear
who's having trouble.

Extending pair programming to groups

2009-10-31T14:34:56Z

In XP, you use pair programming -- a pair of programmers work on a
piece of code together. Can this idea be extended to a larger group of
programmer like say the entire project group?
While this would require greater documentation since more than two
people can't work at one PC, one obvious benefit would be that

titanium ecm2001 crack torrent rapidshare download free dGuMRnz^EN

2009-10-12T03:41:49Z

We can crack or emulate any protection type: Dongle,
Hardlock, Hasp, Serial, Password, Hasp4, Flexlm, Sentinel,
Wibu, Eutron Smartkey, Hasphl, Proteq, All the Protections!!
email = yshowsoft@???
email = yshowsoft at gmail.com
ecm2001 titanium download
ecm2001 titanium rapidshare
titanium ecm2001 torrent

ecm2001 crack torrent rapidshare download free mPCC)aiGuX

2009-10-04T20:20:57Z

We can crack or emulate any protection type: Dongle,
Hardlock, Hasp, Serial, Password, Hasp4, Flexlm, Sentinel,
Wibu, Eutron Smartkey, Hasphl, Proteq, All the Protections!!
email = xshowsoft@???
email = xshowsoft at gmail.com
ecm2001 download
ecm2001 rapidshare
ecm2001 torrent
ecm2001 crack
ecm2001 v 5.3

[ANN] Scrum Project Management in Methods & Tools Fall 2009

2009-09-23T16:13:49Z

Methods & Tools is a free e-magazine for software developers, testers
and project managers. Fall 2009 issue's content:
* Mature Scrum at Systematic
* Implementing Automated Software Testing
* The Spring Framework
* The Learning View
* Time and Synchronization in Executable UML
75 pages of software development knowledge that you can download from

Re: how to avoid continuous integration build problems blocking agile developers

2009-09-12T15:16:49Z

My guess is that a pure XP approach is unsuited to the project you are
describing. I think you'll need to make adjustments for these
problems. You describe the size of the project as "large," whereas XP
was designed for a team of a dozen. You have real-time requirements,
whereas XP was designed on (I think I'm correct in saying) an offline

Re: how to avoid continuous integration build problems blocking agile developers

2009-09-11T20:35:12Z

Do these timing problems show up in production, or are they an
artifact of the way that tests are being written?
John Roth

Re: how to avoid continuous integration build problems blocking agile developers

2009-09-11T07:54:53Z

Yes. The selenium tests are failing due to timing issues. Sometimes
the test code waits for something asynchronous to happen and does not
wait long enough. These errors are intermittant.
Problems in the test code. It is very dangerous to have to wait for
asynchronously computed results in tests.

Re: how to avoid continuous integration build problems blocking agile developers

2009-09-09T08:48:26Z

Can you describe a case where a test passes on the developer's machine
but fails on the server?
What is the cause of the error?

Re: how to avoid continuous integration build problems blocking agile developers

2009-09-08T13:04:16Z

XP doesn't distinguish between unit and integration tests; code
is integrated on the developer's machines. What the integration
system is for is to catch the, hopefully very rare, occasions where
two developers have made incompatible changes and a race
condition occurs.
In the same sense, previously passing automated acceptance tests

Re: how to avoid continuous integration build problems blocking agile developers

2009-09-08T06:59:52Z

I should have mentioned that the failing tests are always at
integration or acceptance level. Of course the unit tests should
always run as part of the build and any unit test failure should cause
the build to fail.
See above.
The test suite IS being run on the developers machine.

Re: how to avoid continuous integration build problems blocking agile developers

2009-09-07T15:45:47Z

The standard XP answer is that you should never have failing
unit tests. Period. End of discussion.
So I'd ask why failing unit tests are happening in the integration
process in the first place? This should be a very unusual occurrence,
not an everyday occurrence.
At a guess, the relevant part of the test suite isn't being run on

Re: How to or should we test scripts?

2009-09-06T18:03:58Z

I have justed to get into this territory. The first thing that was
said when I said "How do I test this shellscript then?" was "It is a
shellscript so it is not portable and wont even execute properly on
windoze". Our build has to work on unix (various flavours) and
windoze. So we converted the scripts to python. This felt like quite a

how to avoid continuous integration build problems blocking agile developers

2009-09-06T17:59:48Z

I have been working on a large agile development and it has made me
think alot about build problems during continuous integration. I see
three problems:
1. the build fails when any of the tests fail. This is the number ONE
reason for the build going red. IMO the build should only go red when
there is a failure to build. Testing is something else. The reason for