base on Learn Go with test-driven development # Learn Go with Tests <p align="center"> <img src="red-green-blue-gophers-smaller.png" /> </p> [Art by Denise](https://twitter.com/deniseyu21) [](https://goreportcard.com/report/github.com/quii/learn-go-with-tests) ## Formats - [Gitbook](https://quii.gitbook.io/learn-go-with-tests) - [EPUB or PDF](https://github.com/quii/learn-go-with-tests/releases) ## Translations - [中文](https://studygolang.gitbook.io/learn-go-with-tests) - [Português](https://larien.gitbook.io/aprenda-go-com-testes/) - [日本語](https://andmorefine.gitbook.io/learn-go-with-tests/) - [한국어](https://miryang.gitbook.io/learn-go-with-tests/) - [Türkçe](https://halilkocaoz.gitbook.io/go-programlama-dilini-ogren/) - [فارسی](https://go-yaad-begir.gitbook.io/go-ba-test/) ## Support me I am proud to offer this resource for free, but if you wish to give some appreciation: - [Tweet me @quii](https://twitter.com/quii) - <a rel="me" href="https://mastodon.cloud/@quii">Mastodon</a> - [Buy me a coffee :coffee:](https://www.buymeacoffee.com/quii) - [Sponsor me on GitHub](https://github.com/sponsors/quii) ## Why * Explore the Go language by writing tests * **Get a grounding with TDD**. Go is a good language for learning TDD because it is a simple language to learn and testing is built-in * Be confident that you'll be able to start writing robust, well-tested systems in Go * [Watch a video, or read about why unit testing and TDD is important](why.md) ## Table of contents ### Go fundamentals 1. [Install Go](install-go.md) - Set up environment for productivity. 2. [Hello, world](hello-world.md) - Declaring variables, constants, if/else statements, switch, write your first go program and write your first test. Sub-test syntax and closures. 3. [Integers](integers.md) - Further Explore function declaration syntax and learn new ways to improve the documentation of your code. 4. [Iteration](iteration.md) - Learn about `for` and benchmarking. 5. [Arrays and slices](arrays-and-slices.md) - Learn about arrays, slices, `len`, varargs, `range` and test coverage. 6. [Structs, methods & interfaces](structs-methods-and-interfaces.md) - Learn about `struct`, methods, `interface` and table driven tests. 7. [Pointers & errors](pointers-and-errors.md) - Learn about pointers and errors. 8. [Maps](maps.md) - Learn about storing values in the map data structure. 9. [Dependency Injection](dependency-injection.md) - Learn about dependency injection, how it relates to using interfaces and a primer on io. 10. [Mocking](mocking.md) - Take some existing untested code and use DI with mocking to test it. 11. [Concurrency](concurrency.md) - Learn how to write concurrent code to make your software faster. 12. [Select](select.md) - Learn how to synchronise asynchronous processes elegantly. 13. [Reflection](reflection.md) - Learn about reflection 14. [Sync](sync.md) - Learn some functionality from the sync package including `WaitGroup` and `Mutex` 15. [Context](context.md) - Use the context package to manage and cancel long-running processes 16. [Intro to property based tests](roman-numerals.md) - Practice some TDD with the Roman Numerals kata and get a brief intro to property based tests 17. [Maths](math.md) - Use the `math` package to draw an SVG clock 18. [Reading files](reading-files.md) - Read files and process them 19. [Templating](html-templates.md) - Use Go's html/template package to render html from data, and also learn about approval testing 20. [Generics](generics.md) - Learn how to write functions that take generic arguments and make your own generic data-structure 21. [Revisiting arrays and slices with generics](revisiting-arrays-and-slices-with-generics.md) - Generics are very useful when working with collections. Learn how to write your own `Reduce` function and tidy up some common patterns. ### Build an application Now that you have hopefully digested the _Go Fundamentals_ section you have a solid grounding of a majority of Go's language features and how to do TDD. This next section will involve building an application. Each chapter will iterate on the previous one, expanding the application's functionality as our product owner dictates. New concepts will be introduced to help facilitate writing great code but most of the new material will be learning what can be accomplished from Go's standard library. By the end of this, you should have a strong grasp as to how to iteratively write an application in Go, backed by tests. * [HTTP server](http-server.md) - We will create an application which listens to HTTP requests and responds to them. * [JSON, routing and embedding](json.md) - We will make our endpoints return JSON and explore how to do routing. * [IO and sorting](io.md) - We will persist and read our data from disk and we'll cover sorting data. * [Command line & project structure](command-line.md) - Support multiple applications from one code base and read input from command line. * [Time](time.md) - using the `time` package to schedule activities. * [WebSockets](websockets.md) - learn how to write and test a server that uses WebSockets. ### Testing fundamentals Covering other subjects around testing. * [Introduction to acceptance tests](intro-to-acceptance-tests.md) - Learn how to write acceptance tests for your code, with a real-world example for gracefully shutting down a HTTP server * [Scaling acceptance tests](scaling-acceptance-tests.md) - Learn techniques to manage the complexity of writing acceptance tests for non-trivial systems. * [Working without mocks, stubs and spies](working-without-mocks.md) - Learn about how to use fakes and contracts to create more realistic and maintainable tests. * [Refactoring Checklist](refactoring-checklist.md) - Some discussion on what refactoring is, and some basic tips on how to do it. ### Questions and answers I often run in to questions on the internets like > How do I test my amazing function that does x, y and z If you have such a question raise it as an issue on github and I'll try and find time to write a short chapter to tackle the issue. I feel like content like this is valuable as it is tackling people's _real_ questions around testing. * [OS exec](os-exec.md) - An example of how we can reach out to the OS to execute commands to fetch data and keep our business logic testable/ * [Error types](error-types.md) - Example of creating your own error types to improve your tests and make your code easier to work with. * [Context-aware Reader](context-aware-reader.md) - Learn how to TDD augmenting `io.Reader` with cancellation. Based on [Context-aware io.Reader for Go](https://pace.dev/blog/2020/02/03/context-aware-ioreader-for-golang-by-mat-ryer) * [Revisiting HTTP Handlers](http-handlers-revisited.md) - Testing HTTP handlers seems to be the bane of many a developer's existence. This chapter explores the issues around designing handlers correctly. ### Meta / Discussion * [Why unit tests and how to make them work for you](why.md) - Watch a video, or read about why unit testing and TDD is important * [Anti-patterns](anti-patterns.md) - A short chapter on TDD and unit testing anti-patterns ## Contributing * _This project is work in progress_ If you would like to contribute, please do get in touch. * Read [contributing.md](https://github.com/quii/learn-go-with-tests/tree/842f4f24d1f1c20ba3bb23cbc376c7ca6f7ca79a/contributing.md) for guidelines * Any ideas? Create an issue ## Background I have some experience introducing Go to development teams and have tried different approaches as to how to grow a team from some people curious about Go into highly effective writers of Go systems. ### What didn't work #### Read _the_ book An approach we tried was to take [the blue book](https://www.amazon.co.uk/Programming-Language-Addison-Wesley-Professional-Computing/dp/0134190440) and every week discuss the next chapter along with the exercises. I love this book but it requires a high level of commitment. The book is very detailed in explaining concepts, which is obviously great but it means that the progress is slow and steady - this is not for everyone. I found that whilst a small number of people would read chapter X and do the exercises, many people didn't. #### Solve some problems Katas are fun but they are usually limited in their scope for learning a language; you're unlikely to use goroutines to solve a kata. Another problem is when you have varying levels of enthusiasm. Some people just learn way more of the language than others and when demonstrating what they have done end up confusing people with features the others are not familiar with. This ends up making the learning feel quite _unstructured_ and _ad hoc_. ### What did work By far the most effective way was by slowly introducing the fundamentals of the language by reading through [go by example](https://gobyexample.com/), exploring them with examples and discussing them as a group. This was a more interactive approach than "read chapter x for homework". Over time the team gained a solid foundation of the _grammar_ of the language so we could then start to build systems. This to me seems analogous to practicing scales when trying to learn guitar. It doesn't matter how artistic you think you are, you are unlikely to write good music without understanding the fundamentals and practicing the mechanics. ### What works for me When _I_ learn a new programming language I usually start by messing around in a REPL but eventually, I need more structure. What I like to do is explore concepts and then solidify the ideas with tests. Tests verify the code I write is correct and documents the feature I have learned. Taking my experience of learning with a group and my own personal way I am going to try and create something that hopefully proves useful to other teams. Learning the fundamentals by writing small tests so that you can then take your existing software design skills and ship some great systems. ## Who this is for * People who are interested in picking up Go. * People who already know some Go, but want to explore testing with TDD. ## What you'll need * A computer! * [Installed Go](https://golang.org/) * A text editor * Some experience with programming. Understanding of concepts like `if`, variables, functions etc. * Comfortable using the terminal ## Feedback * Add issues/submit PRs [here](https://github.com/quii/learn-go-with-tests) or [tweet me @quii](https://twitter.com/quii) [MIT license](LICENSE.md) [Logo is by egonelbre](https://github.com/egonelbre) What a star! ", Assign "at most 3 tags" to the expected json: {"id":"2698","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"