JetBrains realy used pair programming from XP? :)

Yes ;)

You mean, you really pair program with your favourite character? ;)
Dreams eventually come true, don't they? :)

No, I mean pair programming only :)

Stanislav Davydov (JetBrains) wrote:

>No, I mean pair programming only :)
>

>

Religiously, or only part time?
Have you adopted other XP practices?

Alain

time to time

Have you adopted other XP practices?

Is used unit testing, for example? If yes, is it realy easy and good as
promises Kent Beck?

It's true only for me. I can't speak about other team :)

We're using unit testing.
It's not so easy cause it's a lot of tests. But it's really help us to keep code right :)

In article <bm1li2$1mj$1@is.intellij.net>,
"Stanislav Davydov \(JetBrains\)" <stathik@intellij.com> wrote:

We're using unit testing.
It's not so easy cause it's a lot of tests. But it's really help us to keep
code right :)

Did you also implement unit testing on the GUI side? I can write JUnit
tests pretty easily for backend functions, but UI performance and
correctness is a bear without unit tests.

Scott
scott@alodarNOSPAM.com
scott_ellsworth@alumni.hmcNOSPAM.edu
Java and WebObjects consulting

Do any of you jetbrainers or not use JUnit for gui testing? Does it work ok? Does it take a long time to write the JUnit gui tests? Do you use any other tools other than JUnit to accomplish this? Does anyone have an example of a JUnit test written to test a gui?

Charles,

>..use JUnit for gui testing?

>

You could check out Dave Astels' "Test-driven Development: A Practical
Guide".
In that book, he creates an entire gui-based application Test-First.
AFAIR, he mentions 4 ways to test gui, and uses 1 (Jemmy). It's a very
good book.

Alain

i'll check it out. thanks for the reply.

Alexey Efimov wrote:

Is used unit testing, for example? If yes, is it realy easy and good as
promises Kent Beck?

For PerformaSure, we have quite an extensive suite of unit tests that
run as part of the nightly build and cause a build failure for any test
failures.

In addition to the normal functionality tests, we have code analysis
tests which check stuff like the correct class name is used to obtain a
LogCategory instance (similar to log4j Logger), that System.out and
System.err are not used, Exception parameters in catch blocks are used
(i.e. logged in some way or rethrown), etc.

Last night's build ran 35246 tests. A large proportion of those are
dynamically generated code analysis tests though.

It would be difficult to maintain and develop the product without the
unit tests. But it can be very difficult to write unit tests, especially
for code that interacts with the user, or requires a non-trivial
environment (e.g. WebSphere) to execute.

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919