Testing the auto-me-bot export
  ✅ When invoking the application, expect a registration of the events
Testing the auto-me-bot export Test various pull request related configurations
  ✅ When all PR operations are checked, execute all PR related handlers
  ✅ When event payload contains an unsupported event type, do not execute any handlers
  ✅ When event payload event action type is not supported, do not execute any handlers
  ✅ When no operations are checked and config is {"pr":{"unknownHandler":{}}}, do not execute any handlers
  ✅ When no operations are checked and config is {"pr":{}}, do not execute any handlers
  ✅ When no operations are checked and config is {}, do not execute any handlers
  ✅ When no operations are checked and config is null, do not execute any handlers
  ✅ When the autoApprove operation is checked, execute the related handler
  ✅ When the conventionalCommits operation is checked, execute the related handler
  ✅ When the conventionalTitle operation is checked, execute the related handler
  ✅ When the lifecycleLabels operation is checked, execute the related handler
  ✅ When the signedCommits operation is checked, execute the related handler
  ✅ When the tasksList operation is checked, execute the related handler

Testing the pr-auto-approve handler Test handler matching
  ✅ Test an unknown event type, expect a false match
  ✅ Test pull_request event type with an unknown action type, expect a false match
  ✅ Test pull_request event type with opened action type, expect a match
  ✅ Test pull_request event type with synchronize action type, expect a match
Testing the pr-auto-approve handler Test handler running
  ✅ Test a correct scenario with a non 200 response from the API
  ✅ Test a correct scenario with a rejected response from the API
  ✅ Test with a bot sender and allBots set to true in the configuration, expect approve event
  ✅ Test with a non listed user in the configuration, expect no event
  ✅ Test with a user sender listed in the configuration, expect approve event
  ✅ Test with no configuration, expect no event

Testing the pr-conventional-commits handler Test handler matching
  ✅ Test an unknown event type, expect a false match
  ✅ Test pull_request event type with an unknown action type, expect a false match
  ✅ Test pull_request event type with edited action type, expect a match
  ✅ Test pull_request event type with opened action type, expect a match
  ✅ Test pull_request event type with synchronize action type, expect a match
Testing the pr-conventional-commits handler Test handler running
  ✅ Test with listCommits API endpoint response not successful, expect a report indicating a possible API error
  ✅ Test with listCommits API response endpoint promise rejection, expect a report indicating a possible API error
  ❌ Test with one error commit message, expect one error report
	Cannot read properties of undefined (reading 'parserOpts')
  ❌ Test with one good commit message, expect a successful result
	Cannot read properties of undefined (reading 'parserOpts')
  ❌ Test with one non-standard error based a custom configuration, expect a report error
	Cannot read properties of undefined (reading 'parserOpts')
  ❌ Test with one warning commit message, expect one warning report
	Cannot read properties of undefined (reading 'parserOpts')
  ❌ Test with one warning, one error, and one good commit message, expect a report for both the warning and the error
	Cannot read properties of undefined (reading 'parserOpts')

Testing the pr-conventional-title handler Test handler matching
  ✅ Test an unknown event type, expect a false match
  ✅ Test pull_request event type with an unknown action type, expect a false match
  ✅ Test pull_request event type with edited action type, expect a match
  ✅ Test pull_request event type with opened action type, expect a match
  ✅ Test pull_request event type with synchronize action type, expect a match
Testing the pr-conventional-title handler Test handler running
  ❌ Test with a conventional pr title, expect a successful report
	Cannot read properties of undefined (reading 'parserOpts')
  ❌ Test with a long pr title and a custom config set for error, expect a failed report
	Cannot read properties of undefined (reading 'parserOpts')
  ❌ Test with a long pr title and a custom config set for warning, expect a successful report with a warning
	Cannot read properties of undefined (reading 'parserOpts')

Testing the pr-lifecycle-labels Test handler matching
  ✅ Test an unknown event type, expect a false match
  ✅ Test pull_request event type with an unknown action type, expect a false match
  ✅ Test pull_request event type with closed action type, expect a match
  ✅ Test pull_request event type with edited action type, expect a match
  ✅ Test pull_request event type with opened action type, expect a match
  ✅ Test pull_request event type with ready_for_review action type, expect a match
  ✅ Test pull_request event type with reopened action type, expect a match
  ✅ Test pull_request event type with synchronize action type, expect a match
  ✅ Test pull_request_review event type with an unknown action type, expect a false match
  ✅ Test pull_request_review event type with dismissed action type, expect a match
  ✅ Test pull_request_review event type with edited action type, expect a match
  ✅ Test pull_request_review event type with submitted action type, expect a match
Testing the pr-lifecycle-labels Test handler running
  ✅ Test a pr with change requests, expect the changesRequested label to be added to the pr
  ✅ Test a pr with no reviews, expect the reviewRequired label to be added to the pr
  ✅ Test a pr with reviews but no change requests or approvals, expect the reviewStarted label to be added to the pr
  ✅ Test an approved pr with enough approvals, expect the approved label to be added to the pr
  ✅ Test an approved pr with less then enough approvals, expect the moreReviewsRequired label to be added to the pr
  ✅ Test ignore drafts config with a draft pr, expect the check to be skipped
  ✅ Test invalid config, {"ignoreDrafts":false}, expect the check to be neutral
  ✅ Test invalid config, {"labels":{"unknownLabel":"noKnownLabels"}}, expect the check to be neutral
  ✅ Test invalid config, {"labels":{}}, expect the check to be neutral
  ✅ Test invalid config, {}, expect the check to be neutral
  ✅ Test selected lifecycle label is added to the pr, expect the check to succeed
  ✅ Test selected lifecycle label not configured, expect the check to succeed
  ✅ Test with addLabels API endpoint response not successful, expect the check to fail
  ✅ Test with addLabels API endpoint response promise rejection, expect the check to fail
  ✅ Test with getBranchProtection API endpoint response not successful, expect the approved label to be added to the pr
  ✅ Test with getBranchProtection API endpoint response not successful, expect the check to fail
  ✅ Test with getBranchProtection API endpoint response promise rejection, expect the approved label to be added to the pr
  ✅ Test with getLabel API endpoint response promise rejection, expect the check to fail
  ✅ Test with listReviews API endpoint response not successful, expect the reviewRequired label to be added to the pr
  ✅ Test with listReviews API endpoint response promise rejection, expect the reviewRequired label to be added to the pr

Testing the pr-signed-commits handler Test handler matching
  ✅ Test an unknown event type, expect a false match
  ✅ Test pull_request event type with an unknown action type, expect a false match
  ✅ Test pull_request event type with edited action type, expect a match
  ✅ Test pull_request event type with opened action type, expect a match
  ✅ Test pull_request event type with synchronize action type, expect a match
Testing the pr-signed-commits handler Test handler running
  ✅ Test ignored email is ignored, expect a successful check run
  ✅ Test ignored user name is ignored, expect a successful check run
  ✅ Test with listCommits API endpoint response not successful, expect a report indicating a possible API error
  ✅ Test with listCommits API response endpoint promise rejection, expect a report indicating a possible API error
  ✅ Test with one commit signed by a Bot, not author or committer, expect a successful check run
  ✅ Test with one commit signed by someone else (not author/committer), expect a failed check run
  ✅ Test with one commit signed by the author, expect a successful check run
  ✅ Test with one commit signed by the author, with a domainNotFound service error, expect a failed check run
  ✅ Test with one commit signed by the author, with a invalidEmailStructure service error, expect a failed check run
  ✅ Test with one commit signed by the author, with a noMxRecords service error, expect a failed check run
  ✅ Test with one commit signed by the author, with a SMTPConnectionError service error, expect a failed check run
  ✅ Test with one commit signed by the author, with a SMTPConnectionTimeout service error, expect a failed check run
  ✅ Test with one commit signed by the committer, expect a successful check run
  ✅ Test with one unsigned commit, expect a failed check run
  ✅ Test with two commits signed by the author, expect a successful check run
  ✅ Test with two commits, one is unsigned by bot, and one signed by author, expect a successful check run
  ✅ Test with two commits, one unsigned and one signed by the author, expect a failed check run

Testing the pr-tasks-list handler Test handler matching
  ✅ Test an unknown event type, expect a false match
  ✅ Test pull_request event type with an unknown action type, expect a false match
  ✅ Test pull_request event type with edited action type, expect a match
  ✅ Test pull_request event type with opened action type, expect a match
  ✅ Test pull_request event type with synchronize action type, expect a match
Testing the pr-tasks-list handler Test handler running
  ✅ Test with all tasks checked, expect the check to pass with a summary of the completed tasks
  ✅ Test with not tasks, expect the check to fail providing notification indicating no tasks found
  ✅ Test with unchecked tasks, expect the check to fail with a report of the not yet completed tasks