File	Date	Author	Commit
.settings	2012-05-04	yp	[8d43f2] - cleaned up the code base, refactored the test...
src	2012-05-04	yp	[8d43f2] - cleaned up the code base, refactored the test...
.classpath	2012-03-19	yp	[c62387] Updated pom file.
.euml2	2011-12-03	Yury	[dd747d] Added SCM reporting to the Maven site.
.project	2012-03-19	yp	[8b7be3] - clean up.
.umlproject	2011-12-03	Yury	[dd747d] Added SCM reporting to the Maven site.
README.txt	2011-12-03	Yury	[dd747d] Added SCM reporting to the Maven site.
Sel2.11usage.txt	2011-12-03	Yury	[8a6ed2] Created a git project for AutoBlocks
build.xml	2011-12-03	Yury	[8a6ed2] Created a git project for AutoBlocks
input.txt	2011-12-03	Yury	[8a6ed2] Created a git project for AutoBlocks
pom.xml	2012-03-19	yp	[c62387] Updated pom file.
properties.txt	2012-05-04	yp	[8d43f2] - cleaned up the code base, refactored the test...

Read Me

AutoBlocks is designed to be a novel automated testing framework that allows creating tests from the building block classes 
using this hierarchy: tests->test suites->test cases.

Another important feature of the framework is that the tests/workflows can be created dynamically with arbitrary test configurations using the properties file.

Currently, AutoBlocks can run various configurations of pre-built blocks/classes/scripts and can be tried with Selenium 1 or 2, which is configurable via the properties file. 

The framework is still in the works and needs things like telemetry and appropriate input/output data structures for the tests.

TODO:
- add data input/output queues for the blocks/scripts and make them work in a similar
dynamic fashion the workflow configurations in the properties file.
- add basic reporting, telemetry.

Building the project:
- mvn clean install site assembly:assembly OR ant
- The uberjar resulting from assembly:assembly can be used as follows with the text file:
java -jar <uberjar> proeprties.txt

Author: Yury Potapovich.
Created: Dec 2011
Updated: Dec 2011