I started my career in computing with personal projects, and I continue to build and expand my skills with my own projects.
On a recent project, we needed an easy-to-use component testing tool. Let’s take a look at testing React components with Storybook interaction tests.
This setup will switch the database connection when the Cypress tests are running so it won't muddy up the data in other database environments.
Storybook has benefits for teams working on front-end components. Make the most of these benefits by adding interaction tests for components.
One type of app testing I do regularly is a consistency check. I'll explain what I mean and give examples of possible errors this type of testing picks up.
Have you ever introduced a bug that lurked undetected until deployment? I'll describe a couple of these bugs and early-warning systems to catch them.
You probably won't use your checklist to save a life, but it could save your project from bugs! Make sure an item on your list is to check your checklist.
I was happy to learn that a lot of the work to containerize our app for local development could be leveraged for automated testing using Github actions.
When I wanted to find out exactly when my test started failing, I used the Git bisect tool to find the specific commit that caused my test to fail.
While code coverage is not a perfect indicator of a healthy test suite, JetBrains Rider can help identify areas of potential risk in your solution.
Testing a legacy app with Azure Pipelines can be difficult. Here are some tips for creating a CI pipeline for your own Visual Studio Installer Project.
So you’re staring down a big product launch. Instead of watching your [unit] tests fail, how might you monitor the way your launch issues manifest?