Search the Community

Any standards or guidelines you can suggest for ui testing of a product. I have wrote some code with autoit for basic testing.But I want to make it streamlined and more modularized so that we can add more test cases in future and needed we can change it in a simple manner. Any suggestions..

I need to determine a way to get a Test Engineer or QA Tech's attention. Audio may not work as the tester may not have headphones or speakers plugged in. What I was thinking of doing was creating and playing a video that shifts from black to white and back until the tester hits a key, but that may interfere with what we are testing, or if there was a way to do something like this using AutoIt. That is, using AutoIt to Flash the screen, not play the video. Searching the inet for "Flash Video AutoIt" or other combinations brings up lots of answers to Video Flashing problems with monitors, but nothing to help me with this. I am writing tests for a video utility and there are some areas of the test that require the tester to LOOK at the monitor to verify video quality or other things that can only be validated by looking at the screen. Other tests are validated internally and automatically post "Pass" or "Fail" messages to the log file. Yeah I know they are supposed to be watching but they test multiple systems at once and can't watch everything. Are there features of AutoIt that could help me? Thanks JibsMan

I wanted to see who else is using OATS 12?

So I wanted to install Chromium (from the repository where they release hourly builds) and decided to script it. Compiled and script version included in download. Compiled version removed since I need to clear for some upload space... It's just a wrapper for chrome that will point it to a local user data profile directory. Use the "start.exe" to launch the browser. Chrome Portable Manager.rar - (55) previous downloads Oh, and I forgot to mention that I have no idea what will happen on 64bit systems