Re: [Bug-wget] GSoC 2013 project on rewriting Test Suite in Python.

[Darshit Shah]

> Hello, sorry to randomly but in.
>
Hello. Always glad for more inputs.

>
> On Sat, Jun 29, 2013 at 9:59 PM, Darshit Shah <address@hidden> wrote:
> >> An option would be to support XML (e.g. Test-xyz.xml) and a simple
> >> key/value
> >> text file (e.g. Test-xyz.txt). Both, XML and TXT have their pros and
> cons.
> >> So I
> >> won't say, one is better than the other... but it gives contributors a
> >> choice.
> >>
> >> Not a bad idea. Though I would be wary of having two different formats
> in
> > which tests are written. Fragmentation isn't always a good choice.
> > I would prefer to stick to one option. If there are others who too would
> > prefer a TXT config file, I will switch to that.
> >
>
> Is there any reason why the test definitions couldn't be written in
> plain Python?
>
Giuseppe too was of the opinion that I should create the tests in Python
itself. However, my reasons for not depending on any language were that
language-agnostic tests can be re-used if the driver script is changed to
another language in the future.

The TXT format Tim suggested is prety much valid Python syntax
> already. You might need to an import at the top, like "from defaults
> import *".
>
>
Yes, I think by simply importing these tests, we could set the relevant
variables and use them to configure the server. But that also implies using
unsanitized input in our scripts. We should maybe run a sanity check on
them before imports. But handleable.

I think more people are for Text Based files, so maybe I'll shift it in
that direction.

Will require some more time since I should also start working on
implementing a few other features. (Cookie, authentication support, etc)

 --
Thanking You,
Darshit Shah