4paradigm / 4paradigm/OpenMLDB
Do not print table data and excepted exception stack trace for Java UT
Open
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
Now we will get so many error message in Java UT but they are excepted to be failed.
Contributor guide
Research direction
Find the Java unit tests that are expected to fail but currently print excessive error messages, including table data and stack traces. Look for test classes or methods that handle expected exceptions. Modify the test logging configuration or exception handling to suppress the verbose output while keeping the test assertions valid. Run the specific Java UT to verify the output is cleaner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100