This is the home page of Fighting Layout Bugs - a library for automatic detection of layout bugs in web pages.

It was publicly announced on 20th of October 2009 at the Google Test Automation Conference in Zurich:

http://www.youtube.com/watch?v=WY3C6FHqSqQ

Other presentations:

• QCon London, September 2010
• webinale, June 2011 (german)
• Java User Group Berlin Brandenburg, November 2011 (german)

It can be used with Firefox, Google Chrome, and Internet Explorer via the WebDriver implementations provided by Selenium 2.

What does it offer?

Currently there are the following detectors:

• DetectInvalidImageUrls
• DetectTextNearOrOverlappingHorizontalEdge
• DetectTextNearOrOverlappingVerticalEdge
• DetectTextWithTooLowContrast

How to get started?

• If you use Maven, add the following dependency to your pom.xml file:

    <dependency>
        <groupId>com.googlecode.fighting-layout-bugs</groupId>
        <artifactId>fighting-layout-bugs</artifactId>
        <version>0.3</version>
    </dependency>

Alternatively if you do not use Maven, you can download the fighting-layout-bugs-0.3-jar-with-dependencies.jar and add it to the classpath of your Java project. It includes all needed dependencies like the Selenium 2.20 classes and resources.

• Create a test like this:

    FirefoxDriver driver = new FirefoxDriver();
    try {
        String testPageUrl = "http://www.test.de/";
        driver.get(testPageUrl);
        WebPage webPage = new WebPage(driver);
        FightingLayoutBugs flb = new FightingLayoutBugs();
        final Collection<LayoutBug> layoutBugs = flb.findLayoutBugsIn(webPage);
        System.out.println("Found " + layoutBugs.size() + " layout bug(s).");
        for (LayoutBug bug : layoutBugs) {
            System.out.println(bug);
        }
    } catch (Exception e) {
        e.printStackTrace();
    } finally {
        driver.quit();
    }

Feedback

Feedback is highly appreciated. Let us know, if you experience any problems like:

• a detector throws an exception,
• you got a false alarm,
• you have a layout bug, which is not found.

Of course contributions are welcome too, if you like.