|Bradlee Speice 1b498a8bd9 Commit scripts to help building packages||7 years ago|
|debian||7 years ago|
|docs||7 years ago|
|examples||7 years ago|
|include||7 years ago|
|libcvautomation||7 years ago|
|rpm||7 years ago|
|scripts||7 years ago|
|.gitignore||7 years ago|
|AUTHORS||7 years ago|
|COPYING||7 years ago|
|ChangeLog||7 years ago|
|INSTALL||7 years ago|
|Makefile.am||7 years ago|
|NEWS||7 years ago|
|README||7 years ago|
|README.md||7 years ago|
|autogen.sh||7 years ago|
|configure.ac||7 years ago|
|libcvautomation.pc.in||7 years ago|
|libcvautomation_funcs||7 years ago|
|packageDebian.sh||7 years ago|
|packageRPM.sh||7 years ago|
Use OpenCV to create a GUI testing framework - replaces Sikuli, Xpresser
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.)
OpenCV is used for image processing, and XTestExtension is used for driving X11. Reference implementations are given, and they are fairly full-featured.
Place the following content into a file named
[libcvautomation] name=Libcvautomation RPM repository baseurl=http://djbushido.github.com/libcvautomation/rpm enabled=1 gpgcheck=0
Place the following lines into your
#Libcvautomation Repository deb http://djbushido.github.com/libcvautomation/apt libcvautomation/ deb-src http://djbushido.github.com/libcvautomation/apt libcvautomation-source/
The tarball can be downloaded from the downloads page.
Once you have it, just
./configure; make; make install
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!
If you have a suggestion, comment, question, concern, or otherwise, feel free to email me at email@example.com. This product is developed with the community in mind, so if there’s any feedback to be had I welcome it.