harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Kleymenov" <kleyme...@gmail.com>
Subject Re: [bti] Harmony Build and Testing Infrastructure - Directions for further development
Date Wed, 16 May 2007 10:57:29 GMT
Hi,

As a BTI Status Update I'd like to describe the works currently done on it.

First of all - notification publishing functionality has been implemented on
the framework's side. Now, if Integration Scripts for some Test Suite
(TS) do not implement status notification publisher, the default framework's
means will be used. The notifications sent by default publisher include
the following information: build status, build failure message,
errors/warnings occurred during the execution, and files changed in SVN
repository since last successful build.

The following notification configuration parameters are provided by
framework:

    - it's possible to switch between notification sending mode: to send
      notifications every time after the TS execution, or only if its
      execution status has been changed from failed to passed, or from
passed
      to failed. This configuration is done by means of the following
      framework's parameter property:
            framework.parameters.usemail.always=true
      specified in framework.local.properties file in the root BTI
directory.

    - it's possible set up mail server, 'to' and 'from' addresses,
notification
      subject prefix by means of the following framework's parameter
      properties:
            framework.parameters.usemail=smtp.server
            framework.parameters.usemail.to=to@address.org
            framework.parameters.usemail.from=from@address.org
            framework.parameters.usemail.subject.prefix=[build-test alert]

Each particular Test Suite can customize the default message by specific
summary information, can provide attachments to the notification, and
substitute
default notification message with its own.

All this is configured by the following TS-specific parameters:

  ${test.suite}.parameters.cc.summary
    - if contains the path to file, the content of this file will be
prepended
    to the status notification message.
  ${test.suite}.parameters.cc.message
    - if contains the path to file, the content of this file will be used
    instead of the default message.
  ${test.suite}.parameters.cc.attachs
    - coma or space separated list of absolute paths to files to send with
    notification.
  ${test.suite}.parameters.cc.to
  ${test.suite}.parameters.cc.from
    - if defined and contains email addresses, will be used for mail
    notification instead of corresponding global framework's parameters
values.

The values for summary, message, and attachs parameters should be provided
in test suite's parameters.xml files (as it is mostly Test Suite's
implementation-specific information). The values for 'to' and 'from'
parameters should be provided in framework.local.properties file as it is
local BTI configuration information.

There is 'test-mail' target in the root build.xml intended to test the
correctness of mail configuration before BTI execution.

Secondly, some improvements supporting Test Suites execution process have
been
implemented. So <exec-ant> subroutine launching the ant build process has
been
implemented. It wraps the logic used to call and process the execution
status
and output of external ant scripts in one place, and implements some
workarounds
on common problems with absence of junit.jar in ANT_HOME/lib directory,
proxy
settings, and other.

Now along with further TODO's implementation I'm checking the integration
scripts for test suites not integrated in SVN. I'm actualizing them, making
them more BTI compliant and, if it is possible, simplifying them.

If you have any comments regarding implemented improvements, TODO list,
further development directions, and Test Suite integration process,
please, provide them.

Thanks,
Alexander

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message