File	Date	Author	Commit
build	2013-07-05	smarmotte	[a7f601] Updated build scripts.
doc	2014-12-13	ccleaud	[c9ae79] fixed problem with plugins not found when loadi...
src	2014-12-13	ccleaud	[c9ae79] fixed problem with plugins not found when loadi...
test_samples	2014-05-18	ccleaud	[2b8d12] Changelog:
.hgignore	2011-02-23	fcordova	[d073de] (no commit message)
.hgtags	2014-12-13	ccleaud	[7b0293] Added tag release-12a for changeset c9ae79338c0a
readme.txt	2014-05-18	ccleaud	[c1bf2a] Changelog:

Read Me

** readme.txt for ProUnit **

1. Using the RunTime version of ProUnit
  1a. You want to run the GUI part
      1. add full path to prounit_dlcXX.pl in your propath (client + AppServer) - AppServer is not mandatory
      2. run startProUnitGUI.p
      3. optionnaly, you can create a shortcut to start a new Progress OpenEdge session from this program
      4. here is a sample program to start ProUnit from Progress (even AppBuilder):
         ---------------------------------------------
         DEFINE VARIABLE cOldPropath     AS CHARACTER   NO-UNDO.
         
         ASSIGN  cOldPropath = PROPATH
                 PROPATH = "d:\prounit\prounit_dlc10.pl" + "," + cOldPropath.
         RUN startProUnitGUI.p.
         ASSIGN PROPATH = cOldPropath.
         QUIT.
         ---------------------------------------------

  1b. You want to run the batch part
      1. use the GUI part to create a configuration test file (d:/my_config.xml is used in this example)
      2. copy prounit_dlcXX.pl in <ProgressInstallDirectory>/dcl/tty
      3. start the ProEnv script given with your Progress installation
      4. start a Progress session with startProUnitBatch.p as entry point (see online help for batch parameters)
      5. here is a sample script for usage in Windows environment to start ProUnit in batch mode:
         ---------------------------------------------
         @echo off
         _progres -b -p startProUnitBatch.p -param "-projectFile=d:/my_config.xml -resultFile=d:/my_results.xml"
         ---------------------------------------------


2. Adding built-in plugins or built-in templates
  Built-in plugins and templates are embedded in .pl file.
  Directory names are hard coded so you just have to update the directory list:
  - plugins:   see pluginsEdit.w in procedure "loadAvailablePlugins"
  - templates: see suiteRunner.p in procedure "getResultTemplates"


3. Troubles when editing ProUnit sources with AppBuilder?
  3.a.
  - Close any Progress window.
  - Re-register prox.dll using "regsvr32.exe /u %DLC%\bin\prox.dll" then "regsvr32.exe %DLC%\bin\prox.dll".
  - Restart your AppBuilder then retry.

  3.b.
  ProUnit uses ActiveX maybe you don't have installed on yout computer.
  To fix this, install VB .net express edition (2008 for instance).
  This will install and register required ActiveX components.


4. Build and release instructions
   4.a. Compile all sources recursively (with respect of subfolders) and store R-CODES into a folder
   4.b. Build the documentation (double click on "build\build_doc.cmd") - it requires Apache Forrest
   4.c. Start a Progress proenv window, then run "build\create_release.cmd" by drag-dropping script file into the console window
        This will:
        - create a realse folder
        - generate PL file for current version of Progress
        - copy documentation
    4.d. Restart with all versions of Progress


WebSite: http://prounit.sourceforge.net/
  [The ProUnit Team]