[discuss] another use for archetypes?

[Brett Porter <br...@apache.org>]

Hi,

I wanted to discuss if people had any thoughts on how we might use
archetypes to construct test cases friendly for reporting to JIRA. What
would need to be included, and how would the user select the right one?
Would we need to prompt them for certain information?

I realise this gets complicated quickly, but I'm just thinking that at
least the basics of an archetype can be used to quickly establish a test
case, and perhaps we can aid them building on it from there.

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: [discuss] another use for archetypes?

[Jason van Zyl <ja...@maven.org>]

On Sun, 2005-10-09 at 03:20 +1000, Brett Porter wrote:
> Hi,
> 
> I wanted to discuss if people had any thoughts on how we might use
> archetypes to construct test cases friendly for reporting to JIRA. What
> would need to be included, and how would the user select the right one?
> Would we need to prompt them for certain information?

I think there are two things that we can do here with the way archetypes
currently work.

1) To provide a partial archetype for components where simple tests
cases are added to a project. So someone could, for example, easily
create a test case that would get laid down in maven-core to test some
specific issue. We might end up with many test cases but I think this is
ok and we could then more easily map issues to tests cases that resolved
those issues. Here I think all we would have to add now is a parameter
for the name of the test class. 

2) Provide an archetype for an integration test

Currently I'm working with Jorg to make the archetype system better in
terms of prompting for information (parameter metadata), and we could
easily document what archetypes are to be used for particular cases. We
could probably just document the CLI usage to create the appropriate
archeypte for now. IDE support would be better but some documentation
would work for now.

> I realise this gets complicated quickly, but I'm just thinking that at
> least the basics of an archetype can be used to quickly establish a test
> case, and perhaps we can aid them building on it from there.

Absolutely. I stuck this in with the development process issue for now:

http://jira.codehaus.org/browse/MNG-1305

> - Brett
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

you are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of 
dogmas or goals, it's always because these dogmas or
goals are in doubt.

  -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org