GitHub Actions

Simplifying E2E testing in MFA-enabled environments with Playwright's auth sessions

October 23, 2024

A couple of months ago, I found a way to end-to-end test your solutions, which require you to log in on Microsoft with multifactor authentication enabled. The solution is to use a time-based one-time password (TOTP) that you can generate on the fly during your automated tests. info You can read more about the approach in the automating Microsoft 365 login with multi-factor authentication in Playwright tests article.

Fix the Azure Function Node.js GitHub Actions Windows workflow

September 9, 2024

When deploying Node.js-based Azure Functions using GitHub Actions, you might face an issue with the Windows workflow. In the latest template, there is an issue in the build step where the actions/upload-artifact action fails to upload the artifact due to too many files. The problem is caused by the node_modules folder, which contains many files (even for a starter Azure Function project).

Breaking changes in the GitHub upload-artifact action

September 5, 2024

In August 2024, GitHub announced it would exclude hidden files by default in the actions/upload-artifact GitHub Action. If you are using this action in your workflow, you should be aware of this change, as it might break your workflow. info Read more about it on the notice of upcoming deprecations and breaking changes in GitHub Actions runners blog post from GitHub.

Locally running and testing your custom GitHub Action

July 16, 2024

When developing a custom GitHub Action, you should test and run it locally before pushing it to your repository. Initially, I created a script that allowed me to run it locally, but over the weekend, I found a better way by using the @github/local-action command-line tool. Show image GitHub local-action debugger In this post, I will show you how to use the @github/local-action command-line tool to test your custom GitHub Action locally.

Dispatch a GitHub Action workflow with Github script action

July 10, 2024

You can use the GitHub Actions workflow repository_dispatch event trigger to start a workflow by triggering a webhook. I use this event trigger to start a workflow for building my website when I create or update content in my blog repository. Because my website and the blog content are two separate repositories, I must use the repository_dispatch event to trigger the website build workflow.

Using Playwright in combination with the Microsoft Dev Proxy on GitHub Actions

March 29, 2024

Part of the process of testing the Microsoft Dev Proxy on GitHub Actions, was to use it in combination with Playwright. The advantage of this combination is that you can use the same mocked API responses which you use during development to test your solutions. info That way you do not have to write additional code to mock your APIs in Playwright like I explained in the Test the unexpected API results with Playwright mocking article.