briancray

I would suggest also allowing CSS selectors as a fallback. Text changes often whereas a selector will change less often, producing a more reliable point of interaction.

I would also suggest you put a screencast of a hello world. With many people new to testing using headless webkit, they may have the wrong perception of how selenium tests are run. Additionally what may not be obvious to people used to javascript-based headless webkit tests is that Selenium/Helium tests are written in python. Might want to clarify that as well.

Good luck!

The infrastructure for plastic cards will be around for a very long time. I think the author is ignoring the very expensive need for infrastructure changes. It's the same reason why everyone isn't driving around electric cars.

Opinions/feedback welcome.

Looks like they need a better web server to go with that redesign

Can anyone hear the flush sound?

I really like this comment regarding C-oid languages vs. scripting languages: "Premature optimization is usually not worth it."

Good point

Good one, and thanks for the pointer!

Bad title, good points.

I love the recent focus on hiring people, not job descriptions. I saw another article written by David Cancel of Performable on the same subject. Technical skills are important, mind you, but personalities can't be taught.

Wow, we're forgetful, aren't we.

Fun

While I hate to admit it, this point does have merit if it's true.

LOL. Nuff' said.

Good job covering the changes through IE generations of its supposedly future-proof versions.

The only reason in my opinion that IE will continue to be strong in the market is its proprietary ties to the operating system. Which will also remain its most vulnerable point.

Fixed. Cache plugin screwing me.

Thanks!

Works same in the head. All scripts if not set to asynchronous will prevent further rendering of the page until the script has finished loading and running.

I really prefer Chapra's due to the cleanliness of the design and clarity of results.

I agree that there's too much "utopian" technologies out there with impractical implementations. However, Microdata is already seeing Google support. Browser support I think could come, but we have to bring fuel to the microdata conversation rather than waving it off as nonsense.

I'd say that being able to parse XHTML isn't any easier than parsing HTML in that both requires an author who writes strict code. There's HTML strict, too, ya know.

Thanks for the advice Steve!

Is charging monthly for a license that you download a common practice? Obviously, a recurring pricing structure would be my preference if that's realistic. My initial idea was a yearly license.

On the Analytics API front, I have plans to use the API for a SaaS model later on, but right now I wanted to give developers a tool for running flexible but simple server side tests.

I've been using VWO, and highly recommend it.

That's how iPhone game "Pocket God" has done it: http://appadvice.com/appnn/2009/06/app-store-insider-pocket-...

Thanks, and yes--it should do the same for reddit. To take this off of HN, could you e-mail me your browser so I can look into the --> problem

I feel your pain. As do most. =)

Sure - I've read that - but even if you record >10 second visits, you're still not finding out if users did what you wanted them to do based on bounce rate, unless your metric is time on site.

I don't think the 10 second rule minimizes all other points in the article.

By "time-based" do you mean how long they spent on the page?

Well said! Thanks for the comments!