Test cases implemented using junit tests running policies with assertions on return values.
I will try to reproduce all scenario that failed with null pointers etc. I think most of them were solved with PrimaryExpression fix. Secondly, I want to ensure enough coverage before the custom expressions XML patch. -----Message d'origine----- De : Neeraj Joshi [mailto:[EMAIL PROTECTED] Envoyé : jeudi 10 janvier 2008 19:41 À : imperius-dev@incubator.apache.org Objet : Re: test cases Hey Erik, Can you give a brief overview of what you plan to contribute in terms of the test cases. I am not very clear. Are you referring to Apache guidelines for testing? Thanks Neeraj ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Those are my principles. If you don't like them I have others." http://incubator.apache.org/imperius Neeraj Joshi Autonomic Computing Policy Development Tivoli, IBM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Erik Bengtson" <[EMAIL PROTECTED]> 01/10/2008 02:27 AM Please respond to imperius-dev@incubator.apache.org To "Imperius" <imperius-dev@incubator.apache.org> cc Subject Re: test cases Neeraj, As you said It might be a good idea to keep samples and policy files based test cases in the samples project. Let me know if this is aligned to the testing guidelines so I go ahead with tests changes. Erik -- BlackBerry® from Mobistar --- -----Original Message----- From: Kevan Miller <[EMAIL PROTECTED]> Date: Thu, 10 Jan 2008 00:00:17 To:imperius-dev@incubator.apache.org Subject: Re: test cases On Jan 9, 2008, at 5:54 PM, Craig L Russell wrote: > Hi Neeraj, > > On Jan 9, 2008, at 2:44 PM, Neeraj Joshi wrote: > >> Hi Erik, >> So the sample policies were designed as test cases to test the major >> features of SPL. >> That was one of the reasons why they were part of the JavaSPL module >> initially (shipping them as samples was an after thought). >> We have a couple of 'ComputerSystem' related polices those are more >> like >> samples (and there are no junit tests associated with them) >> >> I agree that pure unit tests that don't require visual inspection >> would be >> ideal but IMO its a non-trivial task. If you like we can setup >> conference >> calls to discuss this in more detail? > > Conference calls tend to be problematic with Apache projects. They > are difficult to set up due to time zone issues; no decisions can be > made; anything discussed has to be published on the dev alias so > everyone can participate. > > Basically, it's best just to use this dev alias for discussions... Seconding Craig's advice... --kevan
