dwyl / book Goto Github PK

Hi Curious People!
Do you want to know how to write tests for your _existing code_?
Drop us a comment below so we know this is something you are interested in. 👍

What communicates the various types of testing better?

Building any software project without tests is a house of cards:

You might even build something impressive:

http://franklinta.com/2014/11/30/image-diffing-using-css/

Why should anyone trust what you write? You didn't study this at university...
how can you possibly know what is the "right" way of writing code...?

• Practical Full-Stack Testing
• Practical Full-Stack JS Web App Test Driven Development ? #KeyWordFest 😜

We often hear the word "refactor" in the context of re-writing code...
But is the term appropriately used?

This is the popular image:

We need to derive our own version.

See: http://stackoverflow.com/questions/4130051/software-development-costs-pyramid

TJ updated the website and repo... need to update this.

http://searchenginewatch.com/sew/study/2208496/72-of-consumers-want-mobilefriendly-sites-google-research

Does the fact that 85% of Browsers (in active use today) Support WebSockets mean we should use the feature everywhere? _or_ should we continue to support the 15%?

Can we use WebSockets? http://caniuse.com/#feat=websockets

Given that a picture is worth a thousand words...
http://en.wikipedia.org/wiki/A_picture_is_worth_a_thousand_words

Should we source (stock?) photos for the book to tell stories in fewer words?
e.g: http://www.istockphoto.com/plans-and-pricing
@iteles thoughts?

Also need to discover if someone has the copyright...

This is how I feel every day! 😉

from: https://xkcd.com/386/

Who is the intended audience?

Read an update: http://www.toptal.com/javascript/guide-to-full-stack-javascript-initjs

Need great copy for an intro tweet!

yes, this is a click-bait question... 😉
obviously we can write poor code and still test it and get coverage...

insert example ...

But... we like to think of code coverage in a packaged food analogy:
Imagine you are at the "health food store" and you see tasty-sounding words on a new product: "Vegan, Raw, All-Natural Delicious, etc..." however, no ingredients are listed.
You ask the store assistant: "can you tell me what is in this...?"
she replies: "oh, just avocado, nuts and a dash of formaldehyde"
_Formalda ... WHAT?_ you exclaim as you prepare to leave the store!!
Yes, formaldehyde is a naturally occurring organic compound, which has been used by bad companies to extend the shelf life of "food" see: http://en.wikipedia.org/wiki/Formaldehyde#Contaminant_in_food

We (used to!) eat packaged foods all the time and trust the manufacturers to have our health and best interest at heart... but unless we know everything that goes into those products, and the precise process by which they are produced, we have no idea what we are consuming!

http://www.isbn.nielsenbook.co.uk/controller.php?page=158
http://www.publish-yourself.com/make-it.shtml

Might be worth doing this before commissioning the (back) Cover ... #25

Addressing the issues noted in each of these:

• http://www.laurencegellert.com/2012/08/what-is-a-full-stack-developer/
• http://techcrunch.com/2014/11/08/the-rise-and-fall-of-the-full-stack-developer/
• http://andyshora.com/full-stack-developers.html
• http://www.sitepoint.com/full-stack-developer/

This looks promising:
https://github.com/segmentio/nightmare
Not sure its the best name...

What prior knowledge/experience do people need to have to get started with JS TDD?

What is the Test Anything Protocol (TAP)?
https://testanything.org/

There's a spectrum of "testedness".
It ranges from "we really need to write some tests" (i.e. zero tests!) to "fully automated continuous deployment".

Where does your current project sit?

http://jasonpolites.github.io/tao-of-testing/ch2-1.1.html

Chapter 2 ... :-)

Hint: the answer is _Yes_! 😉

I ask myself this question all the time!

http://www.iceaaonline.com/ready/wp-content/uploads/2014/03/Software-Test-Cost-and-ROI-Galorath-Feb-14-Hunt.pdf

Release Shedule --> Release Schedule
😃

• Istanbul
• Blanket.js: https://github.com/alex-seville/blanket
• JSCover: http://blog.johnryding.com/post/46757192364/javascript-code-coverage-with-phantomjs-jasmine

Reading

• http://blog.johnryding.com/post/46757192364/javascript-code-coverage-with-phantomjs-jasmine

To drive on public roads people are required to pass a driving test, the test proves that the person can drive the vehicle competently and know essential road safety.

There is no (generally accepted) "test" for being a software developer/engineer, so how do you know the people you are working with are any good?

Should we have a chapter on databases?
http://coding-geek.com/how-databases-work/

this was shared by @jackpandas on @foundersandcoders chat.

When a project has been written/deployed without tests, what is the recommended approach for writing retrospective tests?

1. Writing tests first require you to really consider what you want from the code
2. Fast feedback
3. Creates a detailed specification
4. Reduced time in rework
5. Less time spent in the debugger
6. Identify the error/problem quickly
7. Tells you whether your last change (or refactoring) has broken previously working code
8. Allows the design to evolve and adapt to your changing understanding of the problem.
9. Forces radical simplification of the code, you will only write code in response to the requirements of the tests.
10. Forces you to write small classes focused on one thing.
11. Creates SOLID code
12. Cleans Interface
13. Maintainable, Flexible, Easily Extensible
14. The resulting Unit Tests are simple and act as documentation for the code. Since TDD use-cases are written as tests, other programmers can view the tests as usage examples of how the code is intended to work.
15. Shorten the development Time to Market
16. Increase the programmer’s productivity
17. Cut development costs
18. Improves quality
19. Reduces bugs
20. TDD gives programmers the confidence to change the larger architecture of an application when adding new functionality. Without the flexibility of TDD, developers frequently add new functionality by virtually bolting it to the existing application without true integration – clearly, this can cause problems down the road

Addapted from http://apiumtech.com/blog/20-benefits-of-test-driven-development/
Thanks to @sarahabimay @foundersandcoders

(even though jest is the "official" testing framework...) Mocha and Chai appear to be the default choices in the React/Redux world. should we add a section addressing this?

We already have quite a few images...
We need to number them!

Since high school (DT/Art) I've loved the idea of wearing a Lab Coat while working.
Both to protect one's clothing and to encourage an experimentation mindset.

I saw that early on , this tutorial had Chai as a dependency ,
Any reason this was removed? I'm wondering if there's anything wrong with it as I'm just getting into TDD and want to do it correctly ;)

Thanks.

Can we use making tea as an analogy for a workflow in manual testing?

Should you design your own [book] cover: https://medium.com/@samlaing/self-publishing-43d89e6ea260 ?

Given that there's an English saying:

"Don't judge a book by its cover_..." ~ http://en.wikipedia.org/wiki/Don%27t_judge_a_book_by_its_cover

And the fact that people really do judge books by their covers: http://www.huffingtonpost.com/2013/05/30/book-cover-design-indies_n_3354504.html

I'm going to go ahead and publish a contest on 99designs: http://99designs.co.uk/book-cover-design

In order to have repeatable tests it seems a good idea to have a test database populated with known data against which to write the tests. Populating this database is straightforward and resetting it could be as simple as dropping it at the end of the test. But adding an automated drop database to my test scripts seems like a very bad idea since a config error could easily result in dropping a production database. Any suggestions? I'm using MongoDB and Mocha/Karma/Protractor.

This is the book we all wish we had when we started writing code all those years ago...!

https://www.owasp.org/index.php/Appendix_A:_Testing_Tools

Why?

_Situation_: You want to use a service (API) made by someone else in your project, but you don't want to call that API inside your tests because the network is slow/unreliable or simply because the service requires multi-step (user-input) authentication (e.g: OAuth2) and you don't want to go through that in your tests.

What?

In unit testing a _Mock_ is used to simulate an object or response (from an API) in a controlled way.

How?

Lets say you are building an app called "_BroLee?_" that gives people recommendations on when they should carry an umbrella to wear based on the weather conditions in their location.

Example:

_nock_ is made by @pgte and is the _gold standard_ in simplified libraries.

Notes

• Sinon.js is the Grandaddy of Mocking in JavaScript: http://sinonjs.org (I've tried to teach it to complete beginners and most found it confusing, stick to nock and keep it simple)
• The wikipedia article is quite good: https://en.wikipedia.org/wiki/Mock_object

Is there a good comparative article demonstrating the various node.js testing frameworks?

Can we craft better examples...?

See: https://github.com/nelsonic/learn-tdd