Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize the inconsistent logging, asserting, and println approach in JLM system tests #94

Open
Mesbah-Alam opened this issue Mar 29, 2018 · 0 comments

Comments

@Mesbah-Alam
Copy link
Contributor

The reporting and error logging approach in JLM tests is inconsistent. Some of the tests generate "CSV" data files where some info is logged. The rest go into standard err and out. There are also some tests (e.g. VMLogger, where a log file is used to log detailed results of what the invoked Bean API's return. The output handling is not standardized in general.

This issue will track the work of standardizing the inconsistent logging, asserting, and println approach in JLM system tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants