Unit tests

[indam23]

• Create unit tests for custom actions, focusing on external APIs
• Closes add actions unit tests #535
• Rename workflows more intuitively and add action unit testing to CI pipeline
  • remove mergepal - use automerge instead
  • add running unit tests
  • rename workflows & files for what they actually do

[indam23]

@erohmensing not all actions are covered by these, but since it's getting to be a lot of changes already, I think we should get this mergeable and in before adding more. Wdyt?

[erohmensing]

I agree, it makes sense to do it in phases, i'll take a look!

[erohmensing]

Great job with these! The fixtures are super thorough, i appreciate you giving time and thought to how to make these rerunnable without filling up our instance/newsletter with dummy conversations and such 😄
A few overall comments:

• I think it makes sense to keep the functions for getting community events outside of the community event class (still under the same API though, where they currently are), as they aren't particular to specific event instances
• Generally, consistency in the docstrings (uppercase vs lowercase, how the quotes are positioned

Coming back to review the tests themselves tomorrow -- mind blacking them in the meantime? Im so used to it now its faster to read 🙈

[erohmensing]

A few comments got lost in the accodion btw -- about the domain getting reformatted

[erohmensing]

I'm stoked about these! but please also check the comments about the domain, I think it will break the forms as it is currently

[indam23]

@erohmensing I know you already approved, but restructuring the tests to match the actions folder changed enough things that I think it needs another look

[erohmensing]

I think we want to use the rasa_sdk Domain here, which is already a dict

[indam23]

It is, but we want to load the actual domain of the bot - I started using an empty dict, but realized that could mask problems in the case that an action starts looking in the domain.