…mped up version number to v1.4.
… jar to start selenium. This is to avoid conflict in running the WebDriver tests. Deleted the the selenium jar from lib folder. Also, in CustomTestListener, added logging message to indicate the test status on completion.
…e with these documents.
… in the WAAT jar, I now include the jars in a lib directory in the zip file. Also, the WAAT jar is also placed in the lib folder in the zip file.
…ced all tests within the EngineWithSeleniumTest class to run sequentially. In Test Data, added a new property (numberOfEventsTriggered) to enable users to allow testing for number of events reported to Omniture / the Web Analytic tools Bettered the error logging in the Report object sent back to the Test framework. Removed warnings due to implicit use of ArrayList objects. Updated project file to include the resources directory in its library to ensure (log4j) logging continues to work correctly. Updated build file. In the created zip file, we also include the samplescripts (eg: SeleniumScriptRunner)
Instead, now creating a zip file which includes - the jar, sample data, resources (log4j.properties) and docs Updated tests appropriately. Moved the WAAT architecture documents to docs\architecture folder
…. For each section, just provide the actionName, and the list of tags Updated version number for WAAT in waat.properties.
…ium to verify the same. Added license information to all the source code files and also included LICENSE.txt. Added Selenium jars to the lib\tests folder