kode-konveyor / tidy-up

You can find up for grab tasks here:
https://github.com/kode-konveyor/repo-server/issues?q=is%3Aissue+is%3Aopen+label%3A%22up+for+grab%22
0 stars 45 forks source link

RevokeWorkRequestController/Logging #100

Closed magwas closed 4 years ago

magwas commented 4 years ago

Behaviour: RevokeWorkRequestController/Logging

Annotations for the test cases:

@TestedBehaviour("Logging")
@TestedService("RevokeWorkRequestController")

The production code is at com.kodekonveyor.work_request.revoke.RevokeWorkRequestController.java The testcase base should be at com.kodekonveyor.work_request.revoke.RevokeWorkRequestControllerTestBase.java The testcase should probably be at com.kodekonveyor.work_request.revoke.RevokeWorkRequestControllerLoggingTest.java

All activities should be logged with level INFO before anything else is done with the user initiating the activity (if known), and the name of the controller.

The result of all successful activities should be logged with level FINE the name of the controller, id(s) of the result(s) (if there is an id), or the value, using the string SUCCESS

The result of all failures should be logged with level WARNING, with the name of the controller, the string "FAILURE", and the reason of the failure.

The logging is implemented by LoggerService. All other controllers and services should call that.

If the user is not knowns, the "user" parameter must be null.

See https://www.vogella.com/tutorials/Logging/article.html for how to log.

The service:

RevokeWorkRequestController RevokeWorkRequestController

DTOs and Entities:

WorkRequestEntity WorkRequestEntity

If you have questions, see the FAQ, or ask on the development slack channel or ask your mentor.

anish97IND commented 4 years ago

grab

magwas commented 4 years ago

ungrabbing due to inactivity

vendra131 commented 4 years ago

grab