Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of anton.luht@gmail.com designates
 64.233.182.187 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ANo8xGeXc0HI2adfY7dDPLjLcBMYWE07Fme6YHnpXJEXONVw5aVb4tKYB+sB8KMOTqzCEonNHbC5RyvGSN9OwxJdzOw1QyalyXaeilPYbf+xS+U6HMwVc+HtMD3Gw3x/Auff+VT/klKMCoPq7NBKKOun4yCZajhRqsyTU+8HlkE=
Message-ID: <ddda44ee0607280849n3f19ed2h75dcfc267bd8ace4@mail.gmail.com>
Date: Fri, 28 Jul 2006 19:49:17 +0400
From: "Anton Luht" <anton.luht@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: [build-test-infra] Build Test Infrastructure
In-Reply-To: <ddda44ee0607260807h2ffd001bj1b386e96ee6f9864@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <509223F0BF55E74FA1247D17207E7A0C270692@orsmsx419.amr.corp.intel.com>
	 <ddda44ee0607260807h2ffd001bj1b386e96ee6f9864@mail.gmail.com>

Hello,

I know why this thread is so lazy - it's because everybody dislikes QA
& testing :)

> OK, now let me add my $0.02 about my vision about reporting of test
> results. I believe it's better to do this using HTTP rather than mail
> because some people may not have access to SMTP port (for example, be
> behind proxy with Exchange as mail server - I don't really know if it
> provides SMTP service). HTTP is open in most  configurations and it
> was already decided that HDK and tests will be delivered via HTTP.
>
> I see the reporting of the results in the following way: after
> executing tests the script packs results and uploads them (as with
> browser file upload) to the server. After that data is processed on
> server-side - daemons can send periodical e-mails, draw charts,
> reports, lists of top test results contributors, etc.

Nobody criticized this approach so I assume that it's not too bad. I'm
going to implement a sketch for server-side bunch of scripts - one
that accepts uploads and puts them to a temp directory and maybe some
simple reports. They won't use any database. I believe that most
common server-side engine is CGI (not PHP or J2EE) so I'd like to
implement this using Perl CGI scripts. Since this is a first draft,
I'm not going to use advanced templates language like XSLT. Including
HTML output in script is bad idea so I'm going to use something like
HTML::Template [1] for pages generation and CGI::Lite [2] for requests
handling.

Perl is chosen just because it suites well for fast prototyping development.

If nobody objects, I'm going to start coding.

[1] http://html-template.sourceforge.net/
[2] http://search.cpan.org/~smylers/CGI-Lite-2.02/Lite.pm

-- 
Regards,
Anton Luht,
Intel Middleware Products Division

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org