Flume release test plan

jmhsieh edited this page Feb 5, 2011 · 2 revisions

Content Checks:

  • Check documentation version ( ./docs/index.html, and sub documents )

  • Check man pages present ( ./docs/man/* )

Build test:

  • Run ant test to make sure contents build.

Functional tests:

  • Run flume version to make sure version is correct

End to end functional tests:

Start local master/node, then:

  • run end-to-end be/dfo/e2e tests. (make sure perms in temp dir are ok).

  • exercises shell, logical nodes, message delivery.

Windows checks:

  • Test installer