Go to file
Bradlee Speice aff47435a9 Document the "waitfor" command better
Change locations of some other documentation, move information about the wrapper environment variables to the appendix
2012-07-20 12:39:03 -04:00
docs Change doxygen to generate .1 files for cva-match and cva-input 2012-07-20 09:29:21 -04:00
examples Add a function to wait for an image to be displayed 2012-07-20 11:49:18 -04:00
include Document the "waitfor" command better 2012-07-20 12:39:03 -04:00
libcvautomation Add a function to wait for an image to be displayed 2012-07-20 11:49:18 -04:00
rpm Integrate the specfile into autoconf 2012-07-19 16:42:24 -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
autogen.sh Fix a minor ordering issue with autogen 2012-06-23 00:39:22 -04:00
ChangeLog Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
configure.ac Change doxygen to generate .1 files for cva-match and cva-input 2012-07-20 09:29:21 -04:00
COPYING Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
INSTALL Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
libcvautomation_funcs Make the "waitfor" command optional 2012-07-20 11:56:23 -04:00
libcvautomation.pc.in Commit the pkg-config files 2012-07-19 15:12:39 -04:00
Makefile.am Commit the pkg-config files 2012-07-19 15:12:39 -04:00
NEWS Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
README Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
README.md Finish up preparations for release 1.0 2012-06-28 12:57:21 -04:00
TODO.md Add the global TODO file 2012-06-26 16:43:06 -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 XTestExtension is used for driving X11. Reference implementations are given, and they are fairly full-featured.

Where we're headed

Image recognition and basic X automation are done. From here, code more advanced X automations (ex. Giving the library a string of text to enter, rather than just a character at a time), and clean up the code.

After the basic functionality is done (Image recognition and automation) I'll develop python bindings to make interfacing with the library simpler. 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.