Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Unit tests are written using Mocha and run with the PhantomJS headless browser.
To set your environment up for unit testing, run:

Code Block
npm install -g mocha-phantomjs phantomjs

Run unit tests via:

Code Block
mocha-phantomjs public/test/test.htmlmvn test


Ambari Backend Development

  • Following points are borrowed from hadoop wiki:
    • All public classes and methods should have informative Javadoc comments.
    • Do not use @author tags.
    • Code must be formatted according to Sun's conventions, with one exception:
    • Indent two spaces per level, not four.
    • Contributions must pass existing unit tests.
    • The code changes must be accompanied by unit tests. In cases where unit tests are not possible or don’t make sense an explanation should be provided on the jira.
    • New unit tests should be provided to demonstrate bugs and fixes. JUnit (junit4) is our test framework:
    • You must implement a class that uses @Test annotations for all test methods.
    • Define methods within your class whose names begin with test, and call JUnit's many assert methods to verify conditions. Please add meaningful messages to the assert statement to facilitate diagnostics.
    • By default, do not let tests write any temporary files to /tmp. Instead, the tests should write to the location specified by the test.build.data system property.
    • Logging levels should conform to Log4j levels
    • Use slf4j instead of commons logging as the logging facade.
    • Logger name should be the class name as far as possible.

...