You're reading from Go Programming - From Beginner to Professional Learn everything you need to build modern software using Go

Product type Paperback

Published in Mar 2024

Publisher Packt

ISBN-13 9781803243054

Length 680 pages

Edition 2nd Edition

Languages

Tools

HTTP

Concepts

Programming Language

Author (1):

Samantha Coyle

View More author details

Table of Contents (30) Chapters

Preface

1. Part 1: Scripts

2. Chapter 1: Variables and Operators FREE CHAPTER

3. Chapter 2: Command and Control

4. Chapter 3: Core Types

5. Chapter 4: Complex Types

6. Part 2: Components

7. Chapter 5: Functions – Reduce, Reuse, and Recycle

8. Chapter 6: Don’t Panic! Handle Your Errors

9. Chapter 7: Interfaces

10. Chapter 8: Generic Algorithm Superpowers

11. Part 3: Modules

12. Chapter 9: Using Go Modules to Define a Project

13. Chapter 10: Packages Keep Projects Manageable

14. Chapter 11: Bug-Busting Debugging Skills

15. Chapter 12: About Time

16. Part 4: Applications

17. Chapter 13: Programming from the Command Line

18. Chapter 14: File and Systems

19. Chapter 15: SQL and Databases

20. Part 5: Building For The Web

21. Chapter 16: Web Servers

22. Chapter 17: Using the Go HTTP Client

23. Part 6: Professional

24. Chapter 18: Concurrent Work

25. Chapter 19: Testing

26. Chapter 20: Using Go Tools

27. Chapter 21: Go in the Cloud

28. Index

Why subscribe?

29. Other Books You May Enjoy

Code coverage

Understanding the extent of code coverage ensures that your tests adequately exercise your code base. Go provides a built-in tool called cover that generates test coverage reports based on the test cases you have implemented and that it can identify. This is something you can easily add for unit tests and is a new feature that was added in Go 1.20 for integration test code coverage.

Industry standards for application development sit at an 80% code coverage average for projects to strive for. You will typically see the coverage tool used in CI tools that run pull requests against main/master branches to check that there are no large drops in code coverage that have been tested.

You can add the cover flag to calculate test coverage on your test functions. There is also a flag that you can include to specify an output file to generate from the code coverage tool running and gathering its results. This is a useful report to include when your project requires artifacts...