Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-dev] continuous testing

Steffen,

After looking at this for a few days I think there are some problems with this approach that need to be addressed somehow. I've added few comments to the suggested bug report, though it is odd, because report is already closed as resolved.

Anyways, the biggest issue is that it introduced second source of issues that is participating in the code changes (in other words change sets and CVS commits, history, annotations, etc), which is not listed as the project linked issue tracker. So we are losing contextual information about these changes, including the task contexts.

I am not sure what would be the right way to resolve this, but maybe continuous testing tool should use project Bugzilla for all reporting.

 regards,
 Eugene


Steffen Pingel wrote:
It's in CVS in sandbox/org.eclipse.mylyn.test.report. I'll add some documentation about how to run it in the next few days.

Steffen


On Sunday 16 December 2007, Eugene Kuleshov wrote:
  Great stuff Steffen! I wonder if code for your headless application
available? It would be interesting to know how all the pieces are glued
together.

  Thanks

  Eugene

Steffen Pingel wrote:
I am in the process of setting up a continuous build process that will
run the Mylyn AllTests suite and AllPerformanceTest suite nightly. I have
implemented a headless application based on Mylyn that publishes test
results to a Trac repository:

 http://mylyn.eclipse.org/bitten/

Every open ticket corresponds to a failing test in the latest nightly
build. The last comment on a ticket describes the cause of the test
failure including a stack trace. Once a test succeeds the ticket is
closed. It is reopened if a test fails during a future build.

Monitoring tests is easy by creating a query against the repository that
includes all tickets (the repository allows anonymous access). Please
note that some of the tests failed due to running in a deployed
environment.

The goal is to make this a seamless part of the Mylyn development
workflow to help us avoid having failed tests go unnoticed. Please
comment on this bug for feedback and suggestions:

 213100: automate publishing of failed tests
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=213100

Steffen
_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-dev






Back to the top