Deepak Jain

Introduction to  Test-Driven development (TDD): q       Based on business requirements, first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally re-factor the new code to acceptable standards. q    Using TDD to produce code means that developers begin by setting out exactly  what  the code should do rather than beginning with  how  the code should satisfy the requirement. q      JUnit : Most of the projects which use Test-driven development (TDD) for Java development use JUnit to write test. Improvement needed in TDD approach: q      Programmers Perspective -  Programmers always wanted to know: ü     “Where to start” - Every Business Analyst (BA) has their own template for writing the Business Requirement document (BRD). ü     “What to test and what not to test” – Many a times all scenarios are not listed in BRD. No formal agreemen

Introduction to Cucumber: Cucumber is a software testing tool that allows development teams to create software by writing “executable specifications” and create systems from the “outside-in”. In doing so, we can ensure that what we deliver, along with the quality of what we deliver, meets the expectations of the business stakeholders Cucumber introduces the notion of “features” which describe the behavior you wish to test. The feature is then broken down into a number of different “scenarios” which comprise the test you wish to execute which will subsequently validate the feature. Each scenario is further broken down into a number of “steps” which describe the execution path of each scenario. Typically, these follow a strict “given-when-then” format which aids consistency and provides a clear template for writing acceptance tests. Cucumber-JVM  is a Java-based variant of Cucumber. Benefits of Cucumber over JBehave: Reliable Eclipse plug-in support, reducing d