Kalvin Hom (kahom) <kahom@...>
toggle quoted messageShow quoted text
The current tests in the controller project are using JUnit for the individual bundles, and separate integration tests are written in their own bundles using
Pax-Exam. Whenever a commit is checked-in, the Jenkins build also runs the tests, and if any of them fail, it leaves a -1 review in Gerrit saying the build is UNSTABLE.
There’s a wiki page on the integration tests here:
From: discuss-bounces@... [mailto:discuss-bounces@...]
On Behalf Of David Erickson
Sent: Friday, May 31, 2013 10:18 AM
To: Alejandro Avella
Cc: discuss@...; tsc@...
Subject: Re: [OpenDaylight Discuss] [OpenDaylight TSC] Proposed Simultaneous Release Plan
There are existing unit tests within a project, and cross-project integration tests will have to be created prior to a release. One existing project uses Maven and the other is being migrated from Ant to Maven. I don't know that there are any dedicated QA
people, but I consider every programmer a QA person :)
The included in-project unit and integration tests run with Maven would be a good place to start learning.
On 5/30/2013 11:13 PM, Alejandro Avella wrote:
I was wondering if you could provide some details on the test scenarios that you plan to run. Are they Junit test cases? What about for the Integration tests? Is there documentation for the unit and integration tests? Is there a test
plan? Are there QA people involved in this Open Source project? How long does it take to run all the tests? Where can I find more information about how to test OpenDayLight project? I saw on the web page that the team is using Gerrit to trigger Jenkins jobs
after code has been reviewed? What build tools are used in the project (Ant, Maven or others?)
I was trying to find this information on the wiki page, but I couldn't find it. If there is something already written, could you point me to that information?
On Thu, May 30, 2013 at 12:49 PM, Ed Warnicke (eaw) <eaw@...> wrote:
I was asked by the TSC to send out the Proposed Simultaneous Release Plan we discussed
in todays TSC call to the list.
I have made the following edits in response to requests from the TSC since we discussed it:
1) I have switched the mailing list in the Communication Channels section from 'simultaneous-release' to
2) I have added a 'String Freeze' to allow for internationalization to M5.
Rajeev Nagar raised a very important point that I am still not certain how to correctly incorporate,
but I feel should be: Where does documentation live in all of this? I am would love to hear thoughts as to how
to correctly incorporate that :)
TSC mailing list
Discuss mailing list