5

Integration/Functional/Acceptance tests are inherently difficult to maintain for a myriad of reasons: they take a long time to run, are hard to keep green consistently, can fail seemingly randomly, are cumbersome to debug, etc. etc. However, they can be priceless, if one manages to have a reliable non-unit test suite.

Is having such a suite, merely a pipe-dream? How are teams able to manage a consistently green, low maintenance non-unit test suite?

Prem C
  • 85
  • 4
  • Which languages are you considering? – Chetter Hummin Mar 08 '12 at 18:08
  • I am willing to consider any language. I am just looking to collect good practices. I mention some in my presentation on slideshare: http://www.slideshare.net/premanandc/functional-testing-patterns-10987452 – Prem C Mar 19 '12 at 13:11

1 Answers1

1

This won't answer the question fully, but here goes. For Java, I use Junit4 (testing) and EclEmma (code coverage). For Javascript, I use Jasmine (testing) and JSCoverage (code coverage).

Chetter Hummin
  • 6,687
  • 8
  • 32
  • 44