123 reputation
7
bio website autumnator.wordpress.com
location Silicon Valley
age
visits member for 2 years, 11 months
seen Nov 19 at 23:13

Feb
18
comment Automated network capture and analysis?
Yea that's what I figured as one option (as mentioned in question about using pcap libraries). Thanks for providing code example of how to do it.
Feb
18
comment Automated network capture and analysis?
Thanks, that's good to know. Too bad code's not available to share as open source :(
Jan
21
comment Telecom testing - any tool integration and use of test frameworks?
Thanks for the feedback. I'm aware of that, but not all telecom tools offer an API (e.g. legacy telecom tools a decade or more old, in house tools, SIPP). I find it rather interesting that for an open source project, nobody has bothered to expose an API for SIPP, it's all XML input files. Compare that to Selenium for web apps which has rich API.
Jan
20
comment Load Testing, Selenium Vs Jmeter Vs other tools
For Selenium performance testing on client side, while outdated, this is also a good resource: code.google.com/p/selenium-profiler
Oct
4
comment Compare screenshots of rendered web pages
Also wanted to add, Sikuli can be better than Selenium or a complement to Selenium (via tools integration), where Selenium falls short. E.g. where you can't automate/detect object that isn't web-based such as Flash, Silverlight, Java applet, image/video, or combining browser and desktop GUI testing in a single test.
Oct
4
comment Compare screenshots of rendered web pages
On my previous comment, I personally would use Sikuli at the most atomic level for finding/comparing images. That is don't use a whole desktop screenshot as your reference image to find against unless you have to. Always use the smallest portion (e.g. just the object in question, or the object and some other objects relative to it in layout). This will allow for different screen resolutions w/o breaking the test. Whole desktop screenshots dictate you match the screen resolution for it to work.
Oct
4
comment Compare screenshots of rendered web pages
The Sikuli API has parameters for setting level of difference in finding images as well, though it might be less feature rich in how you specify differences compared to other tools or libraries.
Oct
4
comment Compare screenshots of rendered web pages
Well, unless you're comparing against exact match or some specific comparison algorithm or DOM structure, then Sikuli is useful for comparing images or any object/element on the screen/page represented by an image. The method to do this is to capture a reference element/object (say just a button) on the screen (crop it out from a screenshot) or if you need it relative to other objects, then capture a larger portion of screen or even the whole screen. Save the (cropped) capture as reference image. Then use Sikuli API in test to try and find if object exists anywhere on given screen.
Jul
13
comment Under what circumstances is Sikuli better for test automation than Selenium or Watir?
Check out my Sikuli wrapper project that presents a bit of how to appropriately use Sikuli as well as a smaller core subset API of what you would do with Sikuli: code.google.com/p/simplesikuli/wiki/UsageDetails
Jul
13
comment Under what circumstances is Sikuli better for test automation than Selenium or Watir?
had to break up comment due to length. So you do Sikuli tests like can you click this button on screen (doe it exist anywhere on screen)? And you can make it relative to some other elements on screen as in button must be next to these items, etc. How atomic you make it depends on your needs. Fully atomic means it can be anywhere and not relative to some other elements. Using these techniques properly, changes in page layout won't necessarily break a test. You just have to update UI elements when changed (e.g. button look) and page layout only if using relativity of elements to each other.
Jul
13
comment Under what circumstances is Sikuli better for test automation than Selenium or Watir?
I think some people overlook how to really use Sikuli. You don't take a screenshot of whole (web)page & work with it. That's not the point. There are screenshot tools you can use then manually compare or run some tool to compare screenshot to reference image. The way you use Sikuli is to define "atomic" UI elements (i.e. button on page, a link, some text) typically w/o dependency on layout of other elements and save cropped screenshots of them as reference images. Then compare them against what you see on screen at runtime. So you build a repository of graphic UI elements vs web UI locators.
Jul
13
comment Under what circumstances is Sikuli better for test automation than Selenium or Watir?
I don't see how it's better learning AutoIt. Sikuli and AutoIt do about the same things GUI automation of web and desktop apps. Only difference is Sikuli is image based and AutoIt is UI component identifier based. But I have seen cases where AutoIt can't identify a desktop (not browser) UI element, so you'd have to resort to Sikuli, or commercial test tool, or make do with keyboard shortcuts or mouse movements to compensate for not being able to control some UI element.
Jul
13
comment Under what circumstances is Sikuli better for test automation than Selenium or Watir?
again +1 about the desktop testing support.
Jul
13
comment Under what circumstances is Sikuli better for test automation than Selenium or Watir?
One other comment, you're not restricted to using the Sikuli IDE to generate screenshots nor setting precision and positioning. The IDE like Selenium IDE is for throwaway code/tests, and for beginners. There is a robust Java and Python API you can use to build your tests. And you can also manually create your reference image screenshots, just save as PNG format, or call code to dynamically convert from source format to PNG before passing to Sikuli.
Jul
13
comment Under what circumstances is Sikuli better for test automation than Selenium or Watir?
+1, I was just going to comment on this. Nobody else seems to mention that Sikuli and like tools work on desktop and native mobile apps (mobile via emulator) whereas Selenium and Watir are web only.
Jul
13
comment Under what circumstances is Sikuli better for test automation than Selenium or Watir?
Agree wit user867. Screen resolution only comes into play when you want to specifically test against something like a browser window and page rendering at 1024x768. If you're matching/testing against a button or other graphic element, it's size will always be fixed regardless of the screen size, unless someone changed the zoom level of the desktop, etc. And doesn't matter about position of element on screen, Sikuli knows how to find it anywhere on the screen.
Jul
3
comment Is FitNesse the only DSL for Selenium, or is there another DSL available?
I second consideration of Robot Framework. It's the first framework I've seen that offers a great balance between developer programmability with non-programmer usability. There's still a learning curve but it's much more easier to use than say STAF (another test framework), to me anyways. And it's less restricted to some platform unlike Cucumber and RSpec.
Jul
3
comment Is FitNesse the only DSL for Selenium, or is there another DSL available?
Can't say for Cucumber, but there are some benefits to using similar tools like Robot Framework (or own custom framework). One, with the right team, you can have the less skilled QAs and even business stakeholders write the tests, while the automation "architects" create & maintain the keyword libraries used by the framework. So architects manage the actual automation hooks, while the testers and business folks maintain the test coverage. Rather than have people do both. Two, the tests are readable outside of code and IDE. Yes, you can make code readable as keywords, but it's still code.
Jul
3
comment Has someone ever used Selenium RC with Firefox Portable (specifically FF3.6)?
One can also try to run with FF portable w/o specifyinga profile to see if that works as well.