• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

So the moral of the story is coder need to check his code properly, right ?

Ranch Hand
Posts: 1282
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What the heck, it's late on Friday. Plus, this is the intermediate group.

I want to emphasise for all weekend coders of Novice, Beginner and Intermediate Levels.

Within reason, you cannot check your code too much. Often a problem can be coded by figuring out what test it would have to fail to provide much needed design motion when you are stuck.

JavaRanch � Big Moose Saloon � Engineering � Testing

JavaRanch Testing FAQ!
Java Cowboy
Posts: 16084
Android Scala IntelliJ IDE Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Testing is very important in any real project. In the projects I work on, we often use JUnit or TestNG (which is a kind of enhanced version of JUnit) to do automatic tests.
Arch enemy? I mean, I don't like you, but I don't think you qualify as "arch enemy". Here, try this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic