Add test cases for the flaws detected by skipfish

[GoogleCodeExporter]

At the moment there's no explicit and reproducible means to
tell whether skipfish itself functions (or not) (skipfish DOES
function and IS useful, but regressions and other flaws
are inevitable).

What would likely do the job and be maintainable is
a "honepot" URL which skipfish could be exercised against.
With a public URL with well-known HTML gozzintas,
a QA test harness for the now predictable comesouttas
could then be crafted up.

Just in case:
    gossintas/comesouttas == input/output (in amateur radio geek speak)

Original issue reported on code.google.com by n3npq....@gmail.com on 6 Jul 2010 at 11:57

[GoogleCodeExporter]

Another approach (used in neon for WebDAV, quite nice) is to set up a local
HTTP server) that exercises specific functionality. But that's a fair amount
of coding pain to maintain, and some public web site to run skipfish
against is useful not only for specifically testing a skipfish build.

Perhaps there is already a "honeypot" URL somewhere which can be made public?

Original comment by n3npq....@gmail.com on 6 Jul 2010 at 12:14

[GoogleCodeExporter]

A Jarlsberg instance looks like it would be a reasonable starting point for a 
"public" URI for explicitly
testing skipfish detectors.

Original comment by n3npq....@gmail.com on 6 Jul 2010 at 2:53

[GoogleCodeExporter]

That's considerable. I think I have a place for it.

Original comment by piotr.zu...@gmail.com on 6 Jul 2010 at 4:24

[GoogleCodeExporter]

Integrating skipfish with
    http://jarlsberg.appspot.com/
looks like a sound idea (I have no clue about the political correctness
or traffic monitoring policies of course).

Original comment by n3npq....@gmail.com on 6 Jul 2010 at 4:35

[GoogleCodeExporter]

I do have a test suite for skipfish, although it's not included in the tarball. 
Running it against Jarlsberg or other demo site is probably less useful, 
because it does not exercise the skipfish-specific bits particularly well 
(e.g., dictionary-based discovery, link extraction, etc).

I will try to include some test stuff in the future releases, but no guarantees 
on the timeline.

Original comment by lcam...@gmail.com on 23 Nov 2010 at 6:46

• Changed state: WontFix