Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Test Automation Engineering Handbook

You're reading from   Test Automation Engineering Handbook Learn and implement techniques for building robust test automation frameworks

Arrow left icon
Product type Paperback
Published in Jan 2023
Publisher Packt
ISBN-13 9781804615492
Length 276 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Manikandan Sambamurthy Manikandan Sambamurthy
Author Profile Icon Manikandan Sambamurthy
Manikandan Sambamurthy
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1: The Basics
2. Chapter 1: Introduction to Test Automation FREE CHAPTER 3. Chapter 2: Test Automation Strategy 4. Chapter 3: Common Tools and Frameworks 5. Part 2: Practical Affairs
6. Chapter 4: Getting Started with the Basics 7. Chapter 5: Test Automation for Web 8. Chapter 6: Test Automation for Mobile 9. Chapter 7: Test Automation for APIs 10. Chapter 8: Test Automation for Performance 11. Part 3: Continuous Learning
12. Chapter 9: CI/CD and Test Automation 13. Chapter 10: Common Issues and Pitfalls 14. Assessments 15. Index 16. Other Books You May Enjoy Appendix A:Mocking API Calls

Getting more familiar with Git

For quality engineers, being proficient in Git and its usage is as important as their knowledge of test automation frameworks. Committing changes and managing branches are critical tasks that they should know by rote. It not only boosts their productivity but also makes the collaboration with the rest of the engineers seamless. In the next section, let us look a little deeper into committing a change and what goes into a commit message.

Committing a change

In the previous chapter, we briefly looked at what a Git commit command does. The commit command helps save all the changes made in the local repository.

Now, let’s look at the importance of writing a descriptive commit message.

Importance of a commit message

More often than not, every software engineer views the commit history to understand what changes went in and why they were made. Anyone viewing a commit message should be able to get adequate context on why a certain change...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime