To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=87469





------- Additional comments from [EMAIL PROTECTED] Thu Mar 27 15:50:12 +0000 
2008 -------
vg: The thing is that I'd like to be as close to the usual behavior as 
possible.  By 'usual' I mean behavior that is common in the projects using 
autocorf/automake and the alike - there 'check' is the target responsible to 
issue unit tests.

In OOo, things get built by running the 'build' command - so the closest 
resemblance of 'make check' is 'build check' - and that is what I want having 
working ;-)

wrt. the separate tests.lst: Developers should be encouraged to create unit 
tests; which of course starts with easiness and visibility of usage of the 
framework for the test.  prj/tests.lst is visible, unit_test 'job' hidden in 
prj/build.lst is not.

wrt. the dmake 'switch': For dmake, it is not a switch, it is a normal target 
that must be implemented in the test's makefile.mk so that it runs the actual 
test (without that, it just compiles that), like:

check:
    testshl2 blah ugh aoeu

This is necessary because not all tests will use testshl2 framework for 
testing, etc.  And running tests should be a separate task from actually 
building the tests.

All in all ;-) - I don't really care how we actually implement it as long as
- we have a simple and standard-looking way of issuing them (build check)
- it is easy and encouraging for developers to add their tests (so you don't 
have to read tons of documentation to actually learn about some unit_test 
trigger in build.lst [which is cryptic enough by itself already ;-)])

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to