gophercon-2016-cfp-test.md

Type of session: 50 min tutorial

Title

Writing testable code in GO

Abstract

This tutorial will go through the basics on how to write tests in GO and how to write GO code that is testable. We will use an small app to give a clear example on how to test the code. We will cover the build-in test library and the tools to look at the test coverage for your code.

Details

Test driven development is the process of writing tests first for the features you are implementing. In GO if you try to write tests after writing the main code there is a big possibility of getting into a nightmare. The only way you could write tests for your code is if you write code that you can test. This talk with go throug the basics on testing and give a clear example on how to write code that you can test.

The GopherCon 2016 Call for Proposals: http://cfp.gophercon.com/events/gc16

This sounds like an interesting talk! Yea for testing talks :) I understand that English isn't your first language, so first here are my grammar/ language clarity suggestions:

• Capitalize all words in the title except "in"

It's easier to just copy-paste and highly my suggestions so (notice I've added commas too):

This tutorial will go through the basics on how to write tests in GO**,** and how to write GO code that is testable. We will use an small app to give a clear example on how to test the code. We will cover the _built-in_ test library**,** and the tools _you can use_ to look at the test coverage for your code.

Test driven development is the process of writing tests first for the features you are implementing. In GO**,** if you try to write tests after writing the main code**,** there is a big possibility of getting into a nightmare. The only way you could write tests for your code is if you write code that you can test. This talk _will_ go _through_ the basics on testing**,** and give a clear example on how to write code that you can test.

So general suggestions.

• Can you give more details on what the central themes are to writing testable code? This allows you to show the reviewers you know what your talking about (e.g. no conference-driven development), and attendees a better ability to gauge whether the content will be appropriate/interesting for them.
• Who is the intended audience? What proficiency level should they have?
• Is there something new, or something not well understood, or not well appreciated that you are going to talk about? Mention that in the details explicitly.