With the Playwright Trace Viewer, you’ll never need to wonder why your automated browser test failed. The Playwright Trace Viewer makes it easy to record and replay a full trace of everything that happened while running your test!
Accessibility is an important feature of any web application but we often leave it until late in the development process to start testing. With Axe and Playwright, we can easily automate a large amount of Accessibility testing which can help to ensure we don’t ship our apps/sites with Accessibility bugs.
When you have a lot of data in your SQL database, searching for substrings in a column can be slow. Don’t worry, Simon has some terrible awful, no good hacks that will get those queries running as fast as possible.
Azure App Service makes it easy to deploy Web Apps from a Zip file. The Kudu portal provides a simple drag and drop UI for Zip deployments.
Using Azure Automate you can run scheduled tasks inside of Azure to tune resources, do repetitive tasks or event replace entire people on your team.
In this week’s episode, we discuss the mixed metaphors in Playwright naming. Specifically, we take a look at how
pause() and Playwright Inspector can help you to understand what’s happening in your tests and help you to author new tests.
Static Web Apps allows easy build+deploy scenarios for static web sites that use an API backend. In this video we’ll explore the basic concepts and look at hooking up the swa CLI to our pre-compiled as well as our externally hosted apps. Bring your own front end framework or API!
Get the tooling:
GitHub Actions now includes Environments as a first class citizen! You can define environments, including approvals and secrets. See how to easily split your CI/CD workflow into jobs that allow your deployment steps to target a specific environment.
GitHub Environments: https://docs.github.com/en/actions/reference/environments
HTBox/TwoWeeksReady sample: https://github.com/HTBox/TwoWeeksReady/
Writing Azure Functions in C# has traditionally been a cool mashup of DLLs, dependencies and magic while Azure orchestrated the calls for you. But in today’s .NET 5 world, we get to take the reigns back with isolated processes.
In this episode we have a look at some of the changes and benefits of running in an isolated process, and consider some of the implications of those changes as we work with input and output bindings, queues and https triggers.
For more information: https://docs.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-process-guide
It’s common in our application code to want to send out email notifications to users, but when we are testing locally we don’t necessarily want to actually send out emails to a real server. SMTP4Dev makes it easy to test locally with a fake SMPT server that lets you inspect the email messages that you are sending.