search JMRI:

LogixNG

• LogixNG overview
• Package structure
• The Categories enum
• Create Expressions, Actions, and so on
• Sockets
• Plugins for LogixNG
• Unit testing of LogixNG

Development tools

• Getting the code via Git
• Developing with JMRI Code
• Git FAQs
• Building with:
  • Ant
  • NetBeans
  • Eclipse
  • IntelliJ IDEA

Code Structure

• Introduction
• Names and Naming
• Application Structure
• Code Structure Patterns
• Swing Structure
• External Connection Structure
• Application Preferences
• Threading
• Use of XML
  • XML Schema
  • XSLT Formatting
• Web Site
• Javadocs
  • Name Index
  • Packages
  • Classes

Techniques and Standards

• Recommended Practices
• Continuous Integration
• Internationalization
• Logging & Error Handling
• Unit testing with JUnit
• Documentation with Javadoc and UML
• Run the SpotBugs static analysis tool
• Providing help with JavaHelp
• Portable Filename Method
• XML Persistance

How To

• Extend JMRI
• Add a New System
• Add a New Type

Functional Info

• Turnout Feedback
• Network Connections
• How the startup scripts work
• LogixNG

Background Info

• Technology Roadmap
• Survey of JVM Capabilities
• Usage Poll, Spring 2007

Unit testing of LogixNG

Goals for unit testing of LogixNG

There are two main goals with the code that is testing LogixNG.

• The entire code must be tested completely, including every branch. This means that on the coverage report, both "Missed Instructions" and "Missed Branches" should be zero for every class in LogixNG. This goal is impossible to reach entirely, but whenether possible, this goal must be acheived.
• The tests must be as close as possible to "real world" testing. The testing infrastructure must test the code as realisticly as possible.

---