*** Tools and Batch files ***

FlickerToolDriver runs FlickerTool, compares files in Current to Files in Basis. If files are the same, deletes file in Current. If file does not exist in Basis, copies the file from Current to Basis. If files are different, leaves the file in Current.
FlickerDriver <no params> runs Flicker for all subdirectories that have subdirs of Basis and Current where Basis and Current have files
PlansCopy.bat is run any time new test plans are changed or added to BrowserBaseline. Matching directories must exist in FF and IE for PlansCopy to work.

Flicker visually alternates, "flickers", between similarly named images, highlighting the difference.
FlickerTool <dir1> <dir2> <bool> where dir1 is NewCapture(Current) and dir2 is OldCapture(dated dir/Basis) <bool> is copy NewCaptured (files) that do not have a matching (file under) OldCapture


*** How to run tests ***

1. In IntelliJ, run UI_Testing_<browser>
2. Compile application (compiled mode)
3. Launch app in chromeless browser (C:\Flicker\launch_PEDs.html)
4. Run browser specific ScreenCapture (C:\Flicker\ScreenCapture FireFox or C:\Flicker\ScreenCapture IExplorer)
5. Right-click ScreenCaptue tray icon, and select "Capture"
6. Once chromeless app browser window is up, press F12 to launch Testplan steps window
7. Click on app browser window;
8. F12 advances to the next step in the plan, PrintScreen captures the screenshot



NOTE: Any changes to the test plans or introduction of new plans have to happen in C:\zPM\zPEDS\UI_Testing\BrowserBaseline\<TestAreaName>\Plan.xml.
Once done, run C:\zPM\zPEDS\UI_Testing\PlansCopy.bat to copy changes into browser specific directories