Go to file
Bradlee Speice c6c8cf35be Update build dependencies for Python 2012-08-28 15:58:07 -04:00
debian Update build dependencies for Python 2012-08-28 15:58:07 -04:00
docs Add initial libcvautomation_funcs.py and documentation 2012-08-14 13:35:16 -04:00
examples Fix the order of some logic, and fix the eval syntax 2012-08-03 14:12:02 -04:00
include Update other documentation to reflect the new Python wrapper 2012-08-17 15:57:43 -04:00
libcvautomation Add two missing waitFor functions into the C library 2012-08-17 12:06:47 -04:00
m4 Add the python build into Automake to make it portable 2012-08-14 11:53:47 -04:00
python Fix up the Python frame tracing, and make it more portable 2012-08-23 15:43:57 -04:00
rpm Make sure RPM knows about the SWIG library 2012-08-17 16:39:16 -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 Ignore the html/ folder for gh-pages 2012-07-17 16:03:18 -04:00
AUTHORS Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
COPYING Put copyright information in one place 2012-07-23 10:04:34 -04:00
ChangeLog Fix the debian build process up 2012-08-17 17:19:52 -04:00
INSTALL Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
Makefile.am Set up distributing the python bindings 2012-08-13 12:05:42 -04:00
NEWS Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
README Fix a Markdown error 2012-07-25 11:15:29 -04:00
README.md Update the top-level README to reflect the Python wrapper 2012-08-17 16:01:00 -04:00
autogen.sh Fix a minor ordering issue with autogen 2012-06-23 00:39:22 -04:00
configure.ac Update version to 2.0 for python bindings 2012-08-14 15:29:43 -04:00
libcvautomation.pc.in Fix how library dependencies are built 2012-07-23 08:53:32 -04:00
libcvautomation_funcs Update the Bash wrapper command names 2012-08-17 15:35:02 -04:00
packageDebian.sh Fix a minor issue with the packaging script 2012-08-03 14:57:19 -04:00
packageRPM.sh Commit scripts to help building packages 2012-07-30 11:38:42 -04:00

README.md

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 XTestExtension is used for driving X11. Reference implementations are given, and they are fairly full-featured.

Installation Instructions

RPM

Place the following content into a file named /etc/yum.repos.d/libcvautomation.repo:

[libcvautomation]
name=Libcvautomation RPM repository
baseurl=http://djbushido.github.com/libcvautomation/rpm
enabled=1
gpgcheck=0 

APT

Place the following lines into your /etc/apt/sources.list:

#Libcvautomation Repository
deb http://djbushido.github.com/libcvautomation/apt libcvautomation/
deb-src http://djbushido.github.com/libcvautomation/apt libcvautomation-source/ 

Tarball

The tarball can be downloaded from the downloads page. Once you have it, just ./configure; make; make install

Where we're headed

At this point, pretty much everything is functionally done. Python bindings to make interfacing with the library simpler have been developed, and it should mostly be bugfixes from here out. If there are any suggestions, please let me know!

Get in contact

If you have a suggestion, comment, question, concern, or otherwise, feel free to email me at bspeice@uncc.edu. This product is developed with the community in mind, so if there's any feedback to be had I welcome it.