The document discusses the importance of testing code through test-driven development (TDD) and behavior-driven development (BDD). It explains that TDD involves writing tests, watching them fail, making them pass, refactoring, and repeating. BDD is more complex and involves business analysts, developers, and stakeholders specifying desired behaviors as user stories. The document encourages writing unit tests because it allows for quick code changes with confidence, helps understand code design, and documents expected behavior, though it takes time initially.

1. How Important is
Testing.
How Testing makes writing code even more easier!

2. Understanding BDD and TDD
• Test Driven Development in simple form is :
Write your tests.
Watch them fail.
Make them pass.
Refactor.
Repeat.

3. BDD – Behavior Driven
Development
• BDD – Behavior Driven Development on the other hand is a
little more complex. It is more of a team work.
• It is more of how a desired behavior should be specified.
• In this concept, Business Analysts and Developers should
specify behaviors in terms of “User Stories”.
• Involving the stake holders in the implementation process
through outside-in Software Development.
• Now we have our own “Jasmine” which helps us test our
JavaScript code in a more TDD way of style.
• For more information on BDD learn here (Wiki is the
best!)http://en.wikipedia.org/wiki/Behavior-
driven_development

4. Real Code! Wohoo….
• If you're all into Rspec, you’ll see Jasmine Framework very
similar.
describe('JavaScript addition operator', function () {
it('adds two numbers together', function () { expect(1 +
2).toEqual(3);
}); });
• “Describe” and “it” functions – Take two parameters a string
and a function.
• Inside “it” block – Write setup code you need for your test.
• Ready to write the actual test – Start with the “expect”
function.

5. Setting up Jasmine

6. So why the Test??
• Unit tests and test-driven development (TDD) have so many
hidden and personal benefits as well as the obvious ones, you
just can't really explain to somebody until they're doing it
themselves.
• Unit tests allows you to make big changes to code quickly.
• You know it works now for sure (because you’ve run the
tests!)
• When you follow TDD no code is considered as
bad/buggy/annoying.
• Unit test helps you to understand the design of the code that
you’re working on.

7. • “One test is worth a thousand expert opinions”. Imagine you
writing the test and saying with confidence (that damn thing
works!)

8. • Good unit tests can help document and define what
something is supposed to do
• Unit tests help with code re-use. Migrate both your
code and your tests to your new project. Tweak the code till
the tests run again.
• Writing unit tests can consume a lot of time in the beginning
but it’s so much worth it.
Sold!
You know it’s good for you, then why not start testing your code.

9. • Good unit tests can help document and define what
something is supposed to do
• Unit tests help with code re-use. Migrate both your
code and your tests to your new project. Tweak the code till
the tests run again.
• Writing unit tests can consume a lot of time in the beginning
but it’s so much worth it.
Sold!
You know it’s good for you, then why not start testing your code.

10. Resources!
• BDD Wiki
• TDD Wiki
• https://github.com/jasmine/jasmine/wiki
• Rspec Rails
• http://agiledata.org/essays/tdd.html
• http://c2.com/cgi/wiki?TestDrivenDevelopment
Books:
• http://www.amazon.com/Test-Driven-Development-By-
Example/dp/0321146530
• http://www.amazon.com/dp/0596006896/?tag=stackoverfl08
-20
• http://www.growing-object-oriented-software.com/

11. Have fun testing! 
Follow me on Twitter: @SanaNasar_