ansaurus

Question

Answer 1

+2 A:

You can try the acid tests, they are to ensure your program is standards compliant. It's not exactly what you asked for but it's a step in the right direction. Most browsers handle broken pages and quirks in different ways and people don't often want to test to see if their broken site renders brokenly in different browsers so I don't think there is going to be something specifically for you but it wouldn't be that hard to do yourself if you wanted to specifically break your program.

Eg.

<sCriPt
type="text/javascript"
>
/*    <span class="*/>awesome"> // */
</script>
<b <i>>a</></b>
<body type="muscular"></body>
<! text
--

I'd like to point you to Adobe Air, I think it would serve your purposes:

Adobe AIR is a cross-operating system runtime that enables you to use your existing HTML/Ajax, Flex, or Flash web development skills and tools to build and deploy rich Internet applications to the desktop.

Sam152 2009-09-27 12:53:58

Answer 2

+1 A:

Assuming that you're building a web-browser, I'd suggest using your own computer as a server, using Apache, Lighttpd (whether Windows, Linux or Mac); that would be the fastest way, surely?

To create a list of 'broken' pages, use the W3 Validator to validate various pages online, view-source and then save as html, removing various closing tags, nesting <p> tags, removing var-names or semi-colons from JS scripts, using the html 4.1 under an xhtml-strict doctype, etc.

The benefit of this is that you know how they're broken in advance, and what the expected outcome should (or is likely to) be. Also, you don't have to worry (too much) about the network's effect on the render-time.

David Thomas 2009-09-27 13:02:29

ansaurus

tags:

views:

answers:

Is there a site for testing?

related questions