Currently viewing the tag: "TestNG"
A part of our team’s “definition of done” is having unit-tests in place and, unofficially, a minimum of 80% code coverage. Our Maven-based build process runs the tests and then creates code coverage reports in HTML format, that we can then consult in the documentation that Maven generates. Along with other reports, this helps us [...]
When you write developer tests, you start with just a few and as your code base gets larger and larger, so does the number of tests. The build starts to take more and more time and soon you avoid running the build as often as possible. If you get to this, then you need to [...]
Archive
- August 2009 (2)
- June 2009 (4)
- March 2009 (1)
- February 2009 (1)
Tags
Adobe Flash blazeds code coverage component tests custom exception translator eclemma Eclipse eclipse galileo exception filetype flash builder 4 flash builder 4 plug-in Flex Flex formatting Java lcds massively multiplayer online games meaningful exception perforce Spring spring blazeds integration springsource system tests Tanki Online tanks test categories TestNG unit tests vmware
