## Quality Assurance Role  --- We had a go at learning Github Actions through a tutorial where you make a repository and add a .github/workflows folder with a main.yml file and an action-a folder with a Dockerfile, entrypoint.sh file and an action.yml file. To make Github Actions work you have to create a PR on a new branch and watch the workflow run or not :thinking_face: --- When you finish the Github Actions tutorial you get a congratulations Octocat :octopus: :cat:  --- Here's the link to the tutorial we went through and some helpful YAML docs and syntax :point_down: [Github Actions Hello World Tutorial](https://lab.github.com/githubtraining/github-actions:-hello-world) [Learn X in Y Minutes](https://learnxinyminutes.com/docs/yaml/) [YAML Docs](https://yaml.org/) --- YAML syntax is very particular about indenting and spacing, here's a bad example from [Online YAML Validator](http://www.yamllint.com/)  --- And here's how you correctly indent lines in a YAML file  --- ## Testing with Jest [Jest Docs](https://jestjs.io/) --- ## Remember to refactor your code :bulb: We all get caught up with the testing when taking on the role of QA but especially as this week we're working on our final project, refactoring code, clearing unnecessary console.logs() and utilising ESLint and Prettier as VSCode extensions keeps everything clear and concise --- ## The action marketplace  ## Copying YAML code for actions  --- ## Automated checks  --- ## Warning ⚠️ Sluggish to debug! (But good for green squares) 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 --- ## Demo ---