mirror-github-bspeice/libcvautomation
1
0
Fork 0
mirror of https://github.com/bspeice/libcvautomation synced 2024-12-03 05:18:10 -05:00
Code Issues Releases Wiki Activity
201 Commits 6 Branches 10 Tags 10 MiB
C 68.5%
Python 13.9%
Shell 10.4%
M4 6.4%
Makefile 0.8%
master
Go to file
DjBushido 4017b92645 Merge pull request #7 from Red5d/patch-1 
Update README
Change djbushido.github.com to djbushido.github.io
2014-02-06 17:05:49 -05: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 libmath and X11 libs not being linked 2013-06-10 16:56:35 -04:00
include Update other documentation to reflect the new Python wrapper 2012-08-17 15:57:43 -04:00
libcvautomation Fixed coding standard 2013-07-25 12:47:28 +02: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 Fix up the specfile to build on 32-bit 2012-08-30 15:12:55 -04:00
scripts Update scripts/openCVLogo.sh 2013-01-14 17:54:34 -05:00
.gitignore git status clean after build 2013-07-21 11:08:46 +02:00
AUTHORS Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
autogen.sh Fix a minor ordering issue with autogen 2012-06-23 00:39:22 -04:00
ChangeLog Fix the debian build process up 2012-08-17 17:19:52 -04:00
configure.ac Begin version 2.1 of libcvautomation 2012-10-11 17:19:58 -04:00
COPYING Put copyright information in one place 2012-07-23 10:04:34 -04:00
INSTALL Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
libcvautomation_funcs Fix breaking on filenames with spaces 2012-09-07 16:26:10 -04:00
libcvautomation.pc.in Fix how library dependencies are built 2012-07-23 08:53:32 -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
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 Update README 2014-02-06 16:55:35 -05:00
README.md Update the README to link to documentation 2013-07-10 20:48:59 -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

API Documentation

Github hosts the documentation, and it can be found here

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.