Go to file
Bradlee Speice b156f16fe2 Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
debian Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
docs Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
examples Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
include Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
libcvautomation Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
rpm Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -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 timestamp in the changelog 2012-08-03 14:56:52 -04:00
INSTALL Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
Makefile.am Distribute the debian/ and rpm/ directories 2012-07-30 11:05:07 -04:00
Makefile.in Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -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
aclocal.m4 Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
compile Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
config.guess Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
config.sub Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
configure Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
configure.ac Begin version 1.4 Bugfix release branch 2012-07-30 13:04:58 -04:00
depcomp Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
install-sh Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
libcvautomation.pc.in Fix how library dependencies are built 2012-07-23 08:53:32 -04:00
libcvautomation_funcs I still have no idea how Bash expects its eval statements 2012-08-03 14:29:34 -04:00
ltmain.sh Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00
missing Release Libcvautomation 1.4-2 2012-08-03 15:04:34 -04:00

README

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](https://github.com/DjBushido/libcvautomation/downloads) page.
Once you have it, just `./configure; make; make install`


## Where we're headed ##
At this point, most everything is functionally done. I'll develop python bindings to make interfacing with the library simpler, but it will be mostly bugfixes until I can get to those. 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.