Thanks for sharing…

-Sakthi.

I have a simple login page written in extension JS in following way:
Ext.onReady(function()
{
Ext.QuickTips.init();
Ext.form.Field.prototype.msgTarget = ‘side’;
new Ext.Button({
renderTo:’login’,
text: ‘Login’,
width: 800
}).on(‘click’,function()
{
document.forms[0].submit();

});
});

Now when I use selenium testing via browser I get a randomly generated id which when hard coded can very well be used in following way:
selenium.click(“ext-gen26″);

My concern is how to get reference of this generated id, so my selenium test case in JUnit is not dependent on randomly generated ids from Extension JS?

Your suggestions appreciated.

Regards,
Prashant

Prashant, I haven’t worked with Ext so I don’t know exactly how it works, and I don’t know what html it uses to model the button.

You might find this article useful http://www.xeolabs.com/portal/node/34

It’s written in Java and drives Selenium to test an ExtJS UI. Although the framework is in-house and source is not public, I wrote an article on it that you might find useful

http://www.neocoders.com/portal/articles/selenium-and-extjs

cheers,
Lindsay

Thanks Lindsay, an interesting read – everyone go check it out. :)

This brings to mind a technique I’ve been finding myself using on occasion when TDD/BDD’ing code. I’d end up with a fixture looking like this:

[Test]
public void DrawingOnScreen()
{
GivenACanvasOfSize(100,100);
WhenDrawingABlackPixelAtPosition(99,99);
ThenTheResultingPictureShoulBe(expectedBitmap);
}

[Test]
public void DrawingOffScreen()
{
GivenACanvasOfSize(100,100);
WhenDrawingABlackPixelAtPosition(101,99);
ThenTheResultingPictureShouldBe(expectedBitmap);
}
…

The tests are extremely readable and tracable back to stories/requirements, but I must admit having so much refactored untested test-code behind the scenes does make me feel uneasy.

I’ve recently been coaching team members on writing acceptance tests with Selenium.
We havn’t tried any of such techniques (yet), and I too find that the tests focus too much on the task-level (type this and that, click that, assert this textbox etc.) instead of on the activity level (perform an invalid login, assert that we get a “login denied” message etc).

I’m guessing too that stuff like UI-Map can get us closer to an activity-testing DSL, although it has a high learning curve for non-developers to use it. Same with Selenium RC (as opposed to HTML).

– Avi

Referencing the “literate API” example in the comment of my post – command classes provide the same aggregation of activities as methods but allow you to minimise change… it also makes it easier to write the syntactic sugar illustrated in the literate API example I tagged on the foot of the post you’ve referenced.

I’ll put together an example that I can share openly (without restriction of NDAs) and post to my blog in the next week or so (hopefully).

Thanks for the comment Antony. I look forward to seeing the blog post you write. I like to see ‘real’ code examples on the internet for at least 2 reasons: so that I can learn, and so that I have more resources to point people at to help their learning.