Hi,

today I started to write a "test environment" for midgard.

This environment should test midgard functions and report the test
results to somewhere (not implemented) - like rubicon (distributed
tests).

Currently, there are 3 different output-types (html, xml, txt).
The tests can be trigged by the browser.
The XML output can be interesting for reporting (using ruby as "caller",
instead of browser => not implemented).

(I hacked this today watching soccer - so be polite :)

I created some fake tests:

html: <https://suge.zilium.de/mgd/test/?type=html>
txt:  <https://suge.zilium.de/mgd/test/?type=txt> (bad formated)
xml:  <https://suge.zilium.de/mgd/test/?type=xml>

(the server has only a 256 Kb/s upstream (DSL) - so be patient)

The output formats are not pefect. They may give you an idea of how
midgard tests could look like.

Suggestions and volunteers are very welcome.

Next 2 or 3 weeks I'm moving so my time is limited. Sorry

Regards
  Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to