From: Artur Hefczyc <wislaj23@wp...> - 2001-08-29 19:52:32
I got e-mail with some questions, but the questions are more general
and I would like to send answers to every wttools developers.
> The whole project name is, "web test tools." I first had an impression that
> you are making a tool to conduct some system level test to your new web
> services, like stress tests.
> When I got your email, then I thought, "well, it sounds more like an API."
> So, could you tell me, how do you expect end users to use this Java tool?
Please notice that there are tools not one tool. So I am not going to create one
universal tool for every possible test. Instead I would like ot create many
simple tools for testing different kind of WEB services.
There can be set of tools created in Java but not only in Java.
In directory "wttools/src/server/apache_modules" you can find one tools
writen in C. It is apache_module to test special kind of HTTP clients which
I create in my current job.
There are many similiar apache modules which I would like to create for
example which producing proper pages or generates errors and so on.
This is example of test tools at server side.
On the other hand to test different WEB servers we should create some special
WEB clients. We can do it for example in Java language. But as you can know
there is no good internet protocols implementation in standard java lib. So
first we should create some implementations of common internet protocols
(HTTP, FTP, SNMP, SMTP, NNTP, ...)
And java implementation of internet protocols is the first step I can see in
java tools library.
But I expect that similiar protocols and tools library may be created not only
in Java but also in other programming languages. Some tools we can create
in Java and some other tools in C, PERL, LISP and so on. (look in apache modules sample)
> okay -- I was actually waiting for your designs, but could you please tell
> me in email, more about your idea?
The class diagram I promissed to create is for explain how I imagine
our Java protocols implementation library. I try to do it before my leave.
It can't cover all wttools idea!
> I'm interested in these "underneath coding" things rather than more GUI
> things, that's why I'm interested.
There is place for both GUI and "underneath coding" in out tools library.
We can even create some strange HTML pages as a test tools for particular
HTTP browsers behaviour.
> So, could you answer my questions in email? Or I can't really tell you what
> task I want manage right now at this point.
> I'll understand clearly your project that way.
As you can see here is place for many different developing activity.
I prefer at begining to assign task to every developer which is most close
to his preferences and knowledge to get some tools as soon as possible.
And than when we will have "first version" we can decide which tools
we should redesign, which tools are most necessary and so on.
We should talk a lot to proper set tasks and goals for future.
Maybe not only through this mailing list but also on some IRC channel.
I prefer to create many simple test which could be easily performed, installed
and which are easy to learn what they do.