Black Sheep Code

I've added dark mode to this blog.

If using Remix on a serverless platform such as Netlify we can use a build time compilation and barrel files to access frontmatter metadata.

You've inherited a React codebase that has no tests.

CDKTF is a tool that allows us to use fully fledged programming languages to do Terraform deployments, having the advantage of being type safe for one.

React Testing Library is perhaps the most popular tool for testing React applications.

How to use Remix and mdx-bundler to make use of frontmatter headers.

Easy Markdown Editor is a handy markdown editor with formatting keyboard shortcuts.

The presence of state management is often what makes testing an Single Page Application difficult.

Counter-intuitively Etc/GMT+x timezones means the opposite of how they appear in an ISO 8601 formatted date string.

We have an API that makes calls out to a third party - how do we test it?

I propose that the designer and the QA should be one and the same.

We can use a tool called jest-timing-reporter to provide a performance diff in our Github pull request.

Using good ol' Jest to write some contract tests with our OpenAPI generated client SDK.

Blackbox tests do not require knowledge of the implementation details - they're a 'how the consumer sees it' style of test.

Postman has an automated testing feature, but how well does it work?

Syncing Postman with our Github repo, generating queries from our OpenAPI spec.

You can very easily add comment functionality to a webpage via the Github-powered Utterances plugin.

JSON API is an opinionated REST API structuring spec.

We're using msw-auto-mock to generate MSW mocks to test our React application.

A lot of state management frameworks recommend doing API mocking as the testing strategy.

I propose a variation of Conway's Law.

Using Remix to generate a static blog.

We'll use openapi-generators to generate a Go backend and a React frontend.

OpenAPI is a spec for describing HTTP APIs.

Cypress recommends long running tests with lots of assertions.

Making changes in an extensible manner avoids having to do significant code rewrites or being disruptive to downstream consumers of your API.

An unconventional strategy to inject the behaviour of your state management in testing contexts

Working with lists of data for form inputs such as radio buttons or checkboxes is non-trivial.

Avoid make state framework specific calls inside of your React components, and instead access them via hooks.

If we're doing shift-left testing, and developers are writing their own tests - then where does that leave QA?

Contractors are best utilised to plough through a well defined scope of work.