Go to file
2012-06-23 00:39:22 -04:00
examples Fix the build process to support OpenCV 2 (Ubuntu) 2012-06-22 20:06:28 -04:00
include/libcvautomation Fix the build process to support OpenCV 2 (Ubuntu) 2012-06-22 20:06:28 -04:00
libcvautomation Add functions to return the center of a sub-image, rather than top-left corner 2012-06-22 15:38:41 -04:00
scripts Add functions to return the center of a sub-image, rather than top-left corner 2012-06-22 15:38:41 -04:00
.gitignore CVAM: Initial detection program 2012-06-20 16:57:03 -04:00
autogen.sh Fix a minor ordering issue with autogen 2012-06-23 00:39:22 -04:00
configure.ac Fix an improper configure.ac 2012-06-22 23:36:21 -04:00
Makefile.am Formalize the build process and integrate autotools 2012-06-22 13:22:16 -04:00
README.md Fix the README a bit 2012-06-21 12:31:52 -04:00

libcvautomation

Use OpenCV to create a GUI testing framework - replaces Sikuli, Xpresser

Why I'm doing this

In trying to create an application testing framework for the MOSAIC team at the University of North Carolina at Charlotte, I was very discouraged by what was currently offered.

Sikuli represented some great ideas, and the built-in IDE was great. Problem being, it crashed whenever I tried to create the first screenshot. Xpresser also looked like it could be great, but died pretty quickly too. Plus, neither of these programs ran on the Prominent North American Enterprise Linux Vendor's software platform.

As such, starting with a sample OpenCV program to recognize sub-images, I'm attempting to create a GUI testing framework that's more stable, no-questions-asked, simple, and otherwise just usable (specifically from BASH - don't make things more complicated than they need to be).

How it works

OpenCV is used for image processing, and should I get around to automating X, I'll likely be using XTE, or XI2, depending on how easy each is.

Where we're headed

Getting a working program to find sub-images first, add any functionality needed to the library, and then implement X automation