You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Salikh Zakirov (JIRA)" <ji...@apache.org> on 2006/11/09 14:20:39 UTC
[jira] Created: (HARMONY-2131) [drlvm] C++ unit test infrastructure
[drlvm] C++ unit test infrastructure
------------------------------------
Key: HARMONY-2131
URL: http://issues.apache.org/jira/browse/HARMONY-2131
Project: Harmony
Issue Type: New Feature
Components: DRLVM
Environment: Linux/ia32, Windows/ia32
Reporter: Salikh Zakirov
The attached patch provides C++ unit test infrastructure. The infrastructure is useful in stand-alone testing
of custom containers, such as ulist.h (unsorted list), which is used in JVMTI tags implementation.
ulist.h already contains some unit tests, excluded from compilation by #ifndef UNIT_TEST.
The unit tests must be formatted as follows:
#include <unit_test.h>
TEST(unit_test_name) {
/* unit test code */
TRACE("fine-level logging"); // logging can be used as well
LOG("more important logging");
INFO("even more important logging");
WARN("very important logging");
assert(1); // use assert() for verifying correct operation
}
unit_test_name must be a valid C++ identifier. It will be macro-expanded into function name.
The main program of the unit test must be arranged as follows:
#include "unit_test_main.h"
int main (int argc, char** argv) {
run(argc, argv);
}
By default, the unit test runs with INFO-level logging enabled, i.e. WARN and INFO message will be printed out,
while LOG and TRACE will not be. The logging level can be configured in the unit test command line:
-Xtrace -- enable all logging message
-Xlog -- enable WARN, INFO and LOG logging messages
-Xinfo -- enable INFO and WARN logging messages [default]
-Xwarn -- enable only WARN logging messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (HARMONY-2131) [drlvm] C++ unit test
infrastructure
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2131?page=all ]
Gregory Shimansky reassigned HARMONY-2131:
------------------------------------------
Assignee: Gregory Shimansky
> [drlvm] C++ unit test infrastructure
> ------------------------------------
>
> Key: HARMONY-2131
> URL: http://issues.apache.org/jira/browse/HARMONY-2131
> Project: Harmony
> Issue Type: New Feature
> Components: DRLVM
> Environment: Linux/ia32, Windows/ia32
> Reporter: Salikh Zakirov
> Assigned To: Gregory Shimansky
> Attachments: Added-C-unit-test-infrastructure.patch, Added-C-unit-test-infrastructure.patch
>
>
> The attached patch provides C++ unit test infrastructure. The infrastructure is useful in stand-alone testing
> of custom containers, such as ulist.h (unsorted list), which is used in JVMTI tags implementation.
> ulist.h already contains some unit tests, excluded from compilation by #ifndef UNIT_TEST.
> The unit tests must be formatted as follows:
> #include <unit_test.h>
> TEST(unit_test_name) {
> /* unit test code */
> TRACE("fine-level logging"); // logging can be used as well
> LOG("more important logging");
> INFO("even more important logging");
> WARN("very important logging");
> assert(1); // use assert() for verifying correct operation
> }
> unit_test_name must be a valid C++ identifier. It will be macro-expanded into function name.
> The main program of the unit test must be arranged as follows:
> #include "unit_test_main.h"
> int main (int argc, char** argv) {
> run(argc, argv);
> }
> By default, the unit test runs with INFO-level logging enabled, i.e. WARN and INFO message will be printed out,
> while LOG and TRACE will not be. The logging level can be configured in the unit test command line:
> -Xtrace -- enable all logging message
> -Xlog -- enable WARN, INFO and LOG logging messages
> -Xinfo -- enable INFO and WARN logging messages [default]
> -Xwarn -- enable only WARN logging messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (HARMONY-2131) [drlvm] C++ unit test
infrastructure
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2131?page=all ]
Gregory Shimansky resolved HARMONY-2131.
----------------------------------------
Resolution: Fixed
Patch applied at 473089. Please check that it was applied as expected.
I also added svn:ignore property with value
ulist_test.exe
ulist_test.obj
If you create more files which should be ignored, let me know.
> [drlvm] C++ unit test infrastructure
> ------------------------------------
>
> Key: HARMONY-2131
> URL: http://issues.apache.org/jira/browse/HARMONY-2131
> Project: Harmony
> Issue Type: New Feature
> Components: DRLVM
> Environment: Linux/ia32, Windows/ia32
> Reporter: Salikh Zakirov
> Assigned To: Gregory Shimansky
> Attachments: Added-C-unit-test-infrastructure.patch, Added-C-unit-test-infrastructure.patch
>
>
> The attached patch provides C++ unit test infrastructure. The infrastructure is useful in stand-alone testing
> of custom containers, such as ulist.h (unsorted list), which is used in JVMTI tags implementation.
> ulist.h already contains some unit tests, excluded from compilation by #ifndef UNIT_TEST.
> The unit tests must be formatted as follows:
> #include <unit_test.h>
> TEST(unit_test_name) {
> /* unit test code */
> TRACE("fine-level logging"); // logging can be used as well
> LOG("more important logging");
> INFO("even more important logging");
> WARN("very important logging");
> assert(1); // use assert() for verifying correct operation
> }
> unit_test_name must be a valid C++ identifier. It will be macro-expanded into function name.
> The main program of the unit test must be arranged as follows:
> #include "unit_test_main.h"
> int main (int argc, char** argv) {
> run(argc, argv);
> }
> By default, the unit test runs with INFO-level logging enabled, i.e. WARN and INFO message will be printed out,
> while LOG and TRACE will not be. The logging level can be configured in the unit test command line:
> -Xtrace -- enable all logging message
> -Xlog -- enable WARN, INFO and LOG logging messages
> -Xinfo -- enable INFO and WARN logging messages [default]
> -Xwarn -- enable only WARN logging messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-2131) [drlvm] C++ unit test infrastructure
Posted by "Salikh Zakirov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2131?page=all ]
Salikh Zakirov updated HARMONY-2131:
------------------------------------
Attachment: Added-C-unit-test-infrastructure.patch
Updated patch with minor correction to fix compilation on Linux.
Apply with
patch -p0 < .../Added-C-unit-test-infrastructure.patch
> [drlvm] C++ unit test infrastructure
> ------------------------------------
>
> Key: HARMONY-2131
> URL: http://issues.apache.org/jira/browse/HARMONY-2131
> Project: Harmony
> Issue Type: New Feature
> Components: DRLVM
> Environment: Linux/ia32, Windows/ia32
> Reporter: Salikh Zakirov
> Attachments: Added-C-unit-test-infrastructure.patch, Added-C-unit-test-infrastructure.patch
>
>
> The attached patch provides C++ unit test infrastructure. The infrastructure is useful in stand-alone testing
> of custom containers, such as ulist.h (unsorted list), which is used in JVMTI tags implementation.
> ulist.h already contains some unit tests, excluded from compilation by #ifndef UNIT_TEST.
> The unit tests must be formatted as follows:
> #include <unit_test.h>
> TEST(unit_test_name) {
> /* unit test code */
> TRACE("fine-level logging"); // logging can be used as well
> LOG("more important logging");
> INFO("even more important logging");
> WARN("very important logging");
> assert(1); // use assert() for verifying correct operation
> }
> unit_test_name must be a valid C++ identifier. It will be macro-expanded into function name.
> The main program of the unit test must be arranged as follows:
> #include "unit_test_main.h"
> int main (int argc, char** argv) {
> run(argc, argv);
> }
> By default, the unit test runs with INFO-level logging enabled, i.e. WARN and INFO message will be printed out,
> while LOG and TRACE will not be. The logging level can be configured in the unit test command line:
> -Xtrace -- enable all logging message
> -Xlog -- enable WARN, INFO and LOG logging messages
> -Xinfo -- enable INFO and WARN logging messages [default]
> -Xwarn -- enable only WARN logging messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-2131) [drlvm] C++ unit test infrastructure
Posted by "Salikh Zakirov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2131?page=all ]
Salikh Zakirov updated HARMONY-2131:
------------------------------------
Attachment: Added-C-unit-test-infrastructure.patch
Apply with
patch -p1 < ..../Added-C-unit-test-infrastructure.patch
> [drlvm] C++ unit test infrastructure
> ------------------------------------
>
> Key: HARMONY-2131
> URL: http://issues.apache.org/jira/browse/HARMONY-2131
> Project: Harmony
> Issue Type: New Feature
> Components: DRLVM
> Environment: Linux/ia32, Windows/ia32
> Reporter: Salikh Zakirov
> Attachments: Added-C-unit-test-infrastructure.patch
>
>
> The attached patch provides C++ unit test infrastructure. The infrastructure is useful in stand-alone testing
> of custom containers, such as ulist.h (unsorted list), which is used in JVMTI tags implementation.
> ulist.h already contains some unit tests, excluded from compilation by #ifndef UNIT_TEST.
> The unit tests must be formatted as follows:
> #include <unit_test.h>
> TEST(unit_test_name) {
> /* unit test code */
> TRACE("fine-level logging"); // logging can be used as well
> LOG("more important logging");
> INFO("even more important logging");
> WARN("very important logging");
> assert(1); // use assert() for verifying correct operation
> }
> unit_test_name must be a valid C++ identifier. It will be macro-expanded into function name.
> The main program of the unit test must be arranged as follows:
> #include "unit_test_main.h"
> int main (int argc, char** argv) {
> run(argc, argv);
> }
> By default, the unit test runs with INFO-level logging enabled, i.e. WARN and INFO message will be printed out,
> while LOG and TRACE will not be. The logging level can be configured in the unit test command line:
> -Xtrace -- enable all logging message
> -Xlog -- enable WARN, INFO and LOG logging messages
> -Xinfo -- enable INFO and WARN logging messages [default]
> -Xwarn -- enable only WARN logging messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira