Git Revert Explained: Safely Undoing Your Changes
As a collaborator to a project, chances are that you will make a bad commit every once in a while—this is inevitable. In fact, some of the frequently asked questions by Git and GitHub users include “How do I undo a commit I made in Git?” and “How do I revert the commit pushed to GitHub?” That’s why it’s crucial to understand some source code commands such as git revert. Git revert is a source code control command typically known as a way to “undo” commits in Git, but it goes beyond that. Think of git revert as a “get out of jail free card” whenever you make a mistake while collaborating on a project. This article from Anita Ihuman on CloudBees’ blog will look at what revert means in the context of Git’s workflow and the different usage scenarios, using code samples liberally.
Measuring Testing: How to Know If Code Quality Is Improving
When it comes to software quality, many people refer to it as a quasi-mythical, unmeasurable property. On the one hand, we see the truth in acknowledging the nuance and subjectivity in defining a complicated factor such as quality. On the other hand, there must be some objective way to assess the quality of code. Otherwise, we’re doomed to only talk about quality in fuzzy ways without any hope of improving it. In this post, we’ll walk you through the importance of measuring testing so you can improve your QA strategy. Find out more from Carlos Schults on Testim’s blog.
Test Coverage Techniques: The Top Ones You Need
We also updated a post this week on test coverage techniques. Let’s face it: automated testing has won. Sure, manual testing still has its value and place. But having a proper automated testing strategy in place is vital for any modern software organization. The problem is that coming up with a sound testing approach is certainly easier said than done. One of the biggest challenges of testing is knowing when to stop. How much testing is enough? Should we strive to test 100% of our application? Or should we prioritize the areas that are more likely to contain problems? Should we allocate our resources uniformly throughout the application or concentrate our efforts on the most critical modules? In this post on Testim’s blog, you can get an answer to the questions above—and more.