CODEWITHSUNDEEP
javaruby-on-railsunit-testingcross-browsercontinuous-integration
aishwarya
aishwarya

Reputation: 1986

cross browser testing, layout testing and continuous integration

We have a large number of web applications developed at a fast pace. More often than not, we are unable to test them sufficiently on different browsers, leading to issues at times. (At the moment, we rely on developers to test their apps in different browsers.)

I am aware that I can use Selenium remote to test functioning of each app in different browser but that does not test the layout (is the top nav really on the top, does this long text break the layout, etc).

Is there an equivalent UI testing tool that could test not only the functionality but also the layout, even if on a high level?

Ideally, I would like to integrate these tests with a CI tool so we could keep a check on UI regression.

I don't know if this is even possible so checking - How do you test your apps in different browsers on a CI tool ?

Upvotes: 1

Views: 494

Answers (2)

Jay Moorthi
Jay Moorthi

Reputation: 877

Take a look at MogoTest. When I last checked, it detected cross-browser layout differences. I'm sure you could integrate it into a CI workflow.

Upvotes: 1

Gerard
Gerard

Reputation: 4848

I'm pretty sure the CI package from Hudson allows you to specify which browser to use. Failing that, you can specify it in your Junit-exported Selenium Tests. Just keep an array of the browser identifiers and loop over them for each test - bear in mind that taking this road will make it harder to see which browser failed for which test.

Upvotes: 0

Related Questions