Experimental project

This is a sandbox project, which contains experimental code for developer use only.

Currently in development

A module that allows human site testers to do easy, on-site cross-browser testing.

Along with their report, a selected element on the page and the path of the page the module also logs their

  • browser type and version,
  • browser window size (using JavaScript),
  • operating system, and
  • system information.

This module is currently being put into use on several large scale Drupal sites and is of great use to those who have hired people specifically for cross browser testing and want a centralised, on-site resource for easily tracking bugs without the addition of an external issue-tracking platform (and the additional training associated with that).

How it works

Once a user has received the appropriate permissions to use the IssueTracker module, the bottom right hand corner of the window of every page on the site will contain a button labelled 'Issue list'. Clicking this button will reveal issues for the current page as well as the option to add a new report. When adding a new report the tester has the ability to select an element on the page that might be causing the issue (similar to Firebug or 'Inspect Element') for example a div that is incorrectly positioned, type a short report, and then add it to the issue list. A developer can then come along and view issues for every page on the site using the corresponding browser and fix them.

Why it's useful

We recently had a project at the work place I'm contracting at that was really front-end intense and needed a lot of cross browser testing (IE7 and up was guaranteed to the client). We employed Basecamp todo lists as a basic issue tracker for cross browser testing however the lists soon got out of hand and it was difficult to understand some of the issues posted as they didn't have any proper context. With this module the context of every report is obvious as it's provided on screen, on the page that has the issue, with a way of directly finding the element the report is about.

Future plans

It'd be great to integrate this with an issue tracking service in the future as there'd be great benefit in providing this kind of on-site issue tracking for cross-browser testing.

Requirements

This module is about as bog standard as you can get and uses only Drupal core hooks to do it's rendering and JavaScript. The issue button on the bottom right of the screen is actually accomplished with a sized down collapsible fieldset. This module shouldn't interfere with your sites layout or cloud any cross-browser testing.

Project Information