[go: up one dir, main page]

Menu

Tree [75a13b] master / presto /
 History

HTTPS access


File Date Author Commit
 .settings 2010-12-18 Adam Monsen Adam Monsen [fe6409] More WIP on MIFOSBI-144. Rudimentary CSV output...
 src 2011-02-26 Jakub Slawinski Jakub Slawinski [98607a] Extended compareCellValues method to handle ano...
 .gitignore 2010-12-20 Adam Monsen Adam Monsen [a6f93c] Ignore Eclipse IDE .classpath & .project
 README 2010-12-22 Adam Monsen Adam Monsen [d95918] MIFOSBI-144 - more documentation & etc. help
 TODO.otl 2010-12-22 Adam Monsen Adam Monsen [682d53] MIFOSBI-144 finish-up: allow testing reports wi...
 build.gradle 2010-12-21 Adam Monsen Adam Monsen [674c64] Use workaround recommended by adam in irc.codeh...
 install.py 2011-01-07 Adam Monsen Adam Monsen [3f190a] Fix test for output plugin. Add test for i18n b...
 writing_tests.txt 2010-12-22 Adam Monsen Adam Monsen [d95918] MIFOSBI-144 - more documentation & etc. help

Read Me

Pentaho Report Test Framework - "presto"

QUICK START:
    install.py will help you make sure you are ready to run tests. Run that
    first. It will report diagnostics on your dev environment and tell you how
    to run the tests.

how to compile code and run tests:
  * run install.py, follow all instructions
  * execute "ppi_build.sh" in parent dir
  * execute "gradle build" in this dir
  * re-running tests? use "gradle cleanTest test"

how to write tests:
  * see writing_tests.txt

how to develop presto with an IDE
  * Eclipse: "gradle eclipse"
    * don't commit .project or .classpath
    * ignore changes to .settings/
    * if you change dependencies, run "gradle eclipseClasspath"
    * see http://www.gradle.org/eclipse_plugin.html for more info
  * IntelliJ Idea: "gradle idea"

prereqs for running tests:
  * Gradle
  * PDI 4.1.0 w/Reporting Output Step installed
  * set up PDI db connection params
  * create ~/.gradle/gradle.properties which defines mifosNexusUsername mifosNexusPassword

prereqs for test development:
  * Eclipse with Groovy plugin (optional)
  * Python (to run install.py)

conventions:
  * indent all source code with 4 spaces, no tabs
  * don't commit IDE settings (exception: .settings/ dir for Eclipse since, for
    instance, it enforces the use of spaces instead of tabs)

related:
  * http://sandbox.pentaho.com/Pentaho-Data-Integration-Reporting-Plug-in/
  * http://mifosforge.jira.com/browse/MIFOSBI-144
  * http://article.gmane.org/gmane.comp.finance.mifos.devel/10458
  * http://forums.pentaho.com/showthread.php?79085 - Announcement/Poll
  * http://forums.pentaho.com/showthread.php?79709-automated-report-testing
  * http://jira.pentaho.com/browse/PDI-5076
  * http://www.ibridge.be/?p=190 - Another announcement