-
Notifications
You must be signed in to change notification settings - Fork 69
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
CL_AUNIT_ASSERT usage in code-pal #236
Comments
How about if we create a check to search for it? (@SAP/code-pal-for-abap-admin) |
Nice idea! But I think we will have the same known problem as in Y_CHECK_DB_ACCESS_IN_UT when the "failure" is not directly in the examined code (but encapsulated inside of a another call). There are also some frameworks used which do not have the ASSERT directly in the examined/parsed object but where else modularized/encapsulated. Got my point? |
Hm, I see. We can configure the check to run in the test and non-test code, so it covers all the objects. It is a simple read table in the tokens searching for the class name (CL_AUNIT_ASSERT). |
|
Is it an ENHANCEMENT or NEW CHECK ? |
Both:
|
Ps: IF_ABAP_UNIT_CONSTANT does not exist in ABAP 7.40 |
* solves #225 (#231) * Update changelog.txt * y_object_creation_date, fix newlines between methods (#233) * solves #219 (#235) * Update changelog.txt * solves 234 (#237) and improve buffer * Update changelog.txt * Minor Refactoring (#240) * Version 1.08.0 * disabling sorter unit test (compatibility to 7.40) * Deprecated AUnit (#238) * solves #236 * solves #236 * Update changelog.txt * Reverting IF_ABAP_UNIT_CONSTANT Not compatible to ABAP 7.40 (see #241) Co-authored-by: Lars Hvam <larshp@hotmail.com>
* new check #236 * Update check_documentation.md * Create deprecated-classes.md * Update check_documentation.md * Update y_demo_failures.clas.abap
* regression feature (#245) * Update changelog.txt * fixing typo (#247) * Update changelog.txt * Update changelog.txt * Split 'Check LOOP' check (#246) * solves #223 * Update check_documentation.md * Create check-in-loop.md * Update check-in-loop.md * Update check-in-loop.md * Update check-statement-position.md * Update check-in-loop.md Co-authored-by: estevao-schultz-neto-SAP <63100656+estevao-schultz-neto-SAP@users.noreply.github.com> * Update changelog.txt * Coverage Thresholds (#249) * solves #243 * versioning check * fixing version * Update changelog.txt * Update check_documentation.md * Create deprecated-classes.md * Update check_documentation.md * Delete deprecated-classes.md * Deprecated Classes (#248) * new check #236 * Update check_documentation.md * Create deprecated-classes.md * Update check_documentation.md * Update y_demo_failures.clas.abap * Update changelog.txt * fixing dump (c_info > c_note) * new version * solves #252 * solves #198 Co-authored-by: estevao-schultz-neto-SAP <63100656+estevao-schultz-neto-SAP@users.noreply.github.com>
Hi,
according to https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/4e/c2efe26e391014adc9fffe4e204223/content.htm usage of CL_AUNIT_ASSERT is obsolete, I dont think it has any special features over CL_ABAP_UNIT_ASSERT ?
https://github.com/SAP/code-pal-for-abap/search?q=CL_AUNIT_ASSERT
The text was updated successfully, but these errors were encountered: