📷 Photo: Buehler's Clock by Wendy Bayer
Versioning is crucial for maintaining the stability and consistency of your GitHub Actions Reusable Workflows
| #!/bin/sh | |
| # Exit script on any errors | |
| set -e | |
| usage() { | |
| cat << USAGE | |
| Usage: $(basename $0) [-dhin] [IMAGE-NAME] | |
| This performs a docker build of the default Dockerfile in the current |
GitHub Actions is powerful tool for automating workflows within the GitHub ecosystem such as Continuous Integration/Continuos Deployment (CI/CD).
One of its standout features is the ability to create custom actions
that can be tailored to perform specific tasks. Among the different types
This guides you through adding the test data fixture utility factory_bot to your Ruby on Rails RSpec project.
To install factory_bot you will need to...
🙇 📖 I originally learned this from these posts...
This guides you through adding the test expectation-matching utility shoulda-matchers to your Ruby on Rails RSpec project.
To install shoulda-matchers you will need to...
In this third post in this series on the fundamentals of software testing, I finish the topic of which values to test as part of your Verification Testing which I started in my previous post on using Boundary-Value Analysis.
Even if you can test all possible values of what you are testing (also known as the system under test), you do not need to waste
In my last post (and the first of this series), I covered the three items comprising the intent of your testing when adding new behavior or changing existing behavior of your software system. In this post, I cover the most basic concept of which values to test as part of your Verification Testing.
Basically, you want to test the boundaries of the possible values