umustafi opened a new pull request, #3817:
URL: https://github.com/apache/gobblin/pull/3817

   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I 
have checked off all the steps below!
   
   
   ### JIRA
   - [X] My PR addresses the following [Gobblin 
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references 
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1946
   
   
   ### Description
   - [X] Here are some details about my PR, including screenshots (if 
applicable):
   Add basic unit testing framework for 
`DagActionStoreChangeMonitor.processMessage()` function which is used for 
processing `launch`, `kill`, and `resume` flow action events. This is a crucial 
piece of functionality used to launch events, so it needs to be resilient to 
malformed message types and handle them without interrupting the thread 
processing the queue. 
   
   ### Tests
   - [X] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   Tests calling process message on HEARTBEAT, INSERT, UPDATE, DELETE operation 
types. The main functionality we seek to test is to ensure heartbeat type 
messages or messages with null dag action types are handled without throwing a 
`NullPointerException`. The unit tests are rudimentary other than the 
aforementioned functionality, mocking all related classes so their states and 
the actual result of processing the message is not validated at the moment. 
   
   ### Commits
   - [X] My commits all reference JIRA issues in their subject lines, and I 
have squashed multiple commits if they address the same issue. In addition, my 
commits follow the guidelines from "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to