Add test cases for existing events in GitHubEventAction component

[ansh-saini]

Closes #16

Hi, I've setup a basic framework for testing events in this component. For future development, we can just keep adding more objects in the testCases array with the expected output. I've added a testContext key (optional) which can be used to give more context to the test name. Like handling singular and plural cases etc...

I've kept the payload minimal to avoid bloating the file with lots of data. That would've made writing new test cases harder. I would love to know your thoughts on this approach.

[mattxwang]

Hi Ansh, thank you for your contribution! As-is, this looks good. However, I have a few questions for you:

• I'd like to test the content of the links as well (i.e. the href), to see if we properly interpret the API. Is this something you could add to this PR?
• As we add more events, I think inlining everything in the test file itself is probably not sustainable. In addition, we're currently testing a fragment of the data returned, rather than the entire input. Could we:
  • move all the test input data (the "fixtures") to their own file(s)? I think one file per test fixture may make sense, but feel free to give me feedback on this idea.
  • include the entire GitHub API response in the test fixture? instead of just the data that we'd need

[ansh-saini]

Hey, thanks for the review.
We can definitely add tests for the href attribute.
I like the fixtures approach too. It's more maintainable in the long run.

I'll be working on these on the weekend.

[mattxwang]

Hi Ansh, looks good! I've left some very minor (naming-related) comments, but other than that we're in pretty good shape to merge. Thanks for all your work so far!

(p.s. - can you add newlines to the end of your JSON files? leads to clean diffs!)

[mattxwang]

This looks great. Nice job Ansh, the contribution is much appreciated. I'll go ahead and merge.