The document summarizes a meetup on implementing test-driven development (TDD) using Munit 2.0. The agenda includes introductions, an overview of why TDD is useful, how to implement TDD using Munit, and a question and answer session. It then discusses networking time and next steps after the meetup. The document provides background on software testing, the traditional development approach versus TDD, advantages of TDD, and the three laws of TDD. It encourages participants to nominate themselves as future speakers and provide feedback to organizers.

1. [Pune-India]
[23rd November 2019]
TDD using Munit 2.0

2. All contents © MuleSoft Inc.
Agenda
2
• Introductions
• Why TDD
• How to implement TDD using Munit
• Q&A
• What’s next
• Networking time

3. All contents © MuleSoft Inc. 3
Santosh
Ojha
Seemant
Jain
Vikalp Bhalia Mukesh ThakurManish Yadav
Presenters, Organizers and You
A SHOW OF HANDS:
Who is new to this Meetup?
Vishwassingh
Pawar

4. • Build Premise for TDD
• What is TDD
• How to implement using Munit 2.0
Agenda

5. All contents © MuleSoft Inc.
Software Testing : What Where and How
5
What?
Software Testing Definition according to ANSI/IEEE 1059 standard – A process of
analyzing a software item to detect the differences between existing and
required conditions (i.e., defects) and to evaluate the features of the software item.

6. All contents © MuleSoft Inc.
Software Testing : What Where and How
6
Where?
At a high level view there are basically 4 different areas but we would be focusing on Unit Testing
Unit Testing
Integration Testing
System Testing
Acceptance Testing

7. All contents © MuleSoft Inc.
Software Testing : What Where and How
7
How?
The agenda of this session is to focus on achieving Unit Testing using TDD (Test
Driven Development)

8. All contents © MuleSoft Inc.
Traditional Software Approach
8
• Has 3 phases
• Each phase usually spans months
• Testing being the most time
consuming phase
DESIGN
IMPLEMENT
TEST

9. All contents © MuleSoft Inc.
Traditional SW Approach: Problems
9
• Longer testing time
• As many bugs introduced as fixed
• Manual testing is not thorough
• Regression Testing for minor changes
• As product grows time for testing increases
• Time labelled for testing included the bug fixes as well
• Code becomes more fragile as it grows
• Associated costs also increase

10. All contents © MuleSoft Inc.
Size Of Code Vs Cost Of Change
10
SizeofCode
Cost of Change

11. All contents © MuleSoft Inc.
Test Driven Development
11
• Reversal of traditional Software Design
• Test cases
• Follows Red Green Refactor approach
DESIGN/TEST
IMPLEMENT

12. All contents © MuleSoft Inc. 12
• You are not allowed to write any production code unless it is to make
a failing unit test pass
• You are not allowed to write any more of a unit test than is sufficient
to fail; and compilation failures are failures.
• Your are not allowed to write any more production code than is
sufficient to pass the failing unit test
Three Laws of Test Driven Development

13. All contents © MuleSoft Inc. 13
• Reduces debug time
• Improved code quality
• Produces testable Code
• Loosely coupled code
• Makes code malleable
• Living documentation of code
• More control over source code and helps to make changes quickly
Advantages of TDD

14. Networking time
Introduce yourself to your neighbors!

15. All contents © MuleSoft Inc.
Take a stand !
15
• Nominate yourself for
the next meetup speaker
and suggest a topic as
well.

16. All contents © MuleSoft Inc.
What’s next
16
• Share:
– Invite your network to join: https://meetups.mulesoft.com/Pune/
• Feedback:
– Contact your organizers to suggest topics
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
– Your feedback is fuel for us
• Our next meetup:
– Date: TBD
– Location: TBD
– Topic: TBD

17. See you next time
Please send topic suggestions to the organizer