Topic tdd-and-bdd b4usolution
Download as PPTX, PDF1 like393 views
TDD and BDD are software testing methodologies. TDD focuses on writing unit tests before code and uses a red-green-refactor cycle. BDD expands on TDD with a focus on defining desired behaviors in business-friendly language to improve collaboration between teams. Key benefits of BDD include stronger collaboration, improved visibility, a shared language, and ensuring software meets business needs. BDD tools like Cucumber use a Given/When/Then syntax to define scenarios in plain text.
Topic tdd-and-bdd b4usolution
- 1. Presentations TDD AND BDD TOPIC: Subject: SOFTWARE TESTING Teacher: Le Thi Bich Hoa Class: D14CQCP01-N Group 7
- 2. Include Three Sections: I. TDD II.BDD III.DIFFERENCES AND CONTRADICTIONS IV.DEMO
- 3. Introduction in TDD: - TDD is a software development process based on the repetition of a very short development cycle: instead of the technical requirements, the test cases are very specific, then the software is modified. Only to pass the new test. This is in contrast to software development that allows adding features that have not been proven to meet the requirements. - Kent Beck, who is credited with developing or rediscovering this programming technique, stated in 2003 that TDD supports simple and highly reliable designs. Test-driven development relates to eXtreme Programming's pre-test programming concepts, launched in 1999, but more recently has created more general interest in its own right. I. TDD
- 4. Test first and test last
- 5. TDD Rhythm TDD is described by a basic red-green-refactor cycle, constantly repeatead to add new features or fix bugs.
- 6. The development of every new feature should start with a failing test. Improve the structure of the code to ease future changes and maintenance. Enough production code should be written to make the test pass. TDD RHYMTHM
- 7. Crucial design principles Do not allow writing any program code until it fails a failed test. Not allowed to write more than one unit test if only one unit test was enough to fail. Let's write code function to pass that test first. It is not allowed to write more than one program code which is enough to make a failed test switch to pass.
- 8. - Write tests first - Write enough code to fail the (first) test - Subsequent code updates and testing - It’s about testing, not about writing specs - Acceptance testing to prevent new software bugs Driving design using TDD It’s a collaborative process – TDD specialist Gojko Adzic stresses the collaborative nature of TDD. The number of people that actually need to be involved depends very much on the nature of the product. For instance, if you are working on a new product or feature then it would be a good idea to have regular small workshops with the “Three Amigos”; a developer, a tester and a business analyst. In contrast, when the product is more mature it might just be a case of pairing two developers to work on it.
- 9. Different style of TDD ATDD Acceptance test–driven development A development methodology based on communication between the business customers, the developers, and the testers. Encompasses many of the same practices as specification by example, behavior-driven development (BDD), example-driven development (EDD), and support-driven development also called story test–driven development (SDD).
- 10. II. BDD WHAT is BDD? Behavior driven development, or BDD, is another agile software development process that encourages collaboration in a software project between developers, QA, project managers and the business team. It was invented in 2003 by Dan North as a response to test-driven development (TDD). On the “Agile specifications, BDD and Testing eXchange” in November 2009 in London, Dan North gave the following definition of BDD, which I actually really liked: “BDD is a second-generation, outside–in, pull-based, multiple-stakeholder, multiple-scale, high-automation, agile methodology. It describes a cycle of interactions with well-defined outputs, resulting in the delivery of working, tested software that matters.” - It enables the technical team and the business team to reach their end goals. In fact, it helps when it comes to defining the desired business outcomes, to communicating what needs to be built by the developer and to understanding what are the technical challenges they might encounter. - Basically, with BDD you focus on getting a clear understanding of the software behavior you are aiming for, by communicating with stakeholders. So developers keep their focus on why a code should be created instead of putting too much emphasis on technical details.
- 11. How do you use them in BDD?
- 12. The customer describes what they want and the developers ask questions to flesh out enough detail about the behaviour to be able to code it. Together with the tester they can then run through many real world examples to derive the scenarios which need to be tested before the story is accepted as “done”. How do you use them in BDD?
- 13. Strong collaboration. High visibility The ubiquitous language The software design follows business value. Software development meets user need More confidence from the developer’s side. A few benefits you get by doing BDD Lower costs Key benefits of BDD
- 14. Key benefits of BDD • With BDD, all the involved parties have a strong understanding of the project and they can all have a role in the communication and actually have constructive discussions. BDD increases and improves collaboration. It enables everyone involved in the project to easily engage in the product development cycle. And by using plain language, all are able to write behavior scenarios. Strong collaboration • By using a language understood by all, everyone gets a strong visibility into the project’s progression. High visibility • By improving the quality of the code, you are basically reducing costs of maintenance and missing the project’s risks. Lower costs • Teams using BDD are in general much more confident that they won’t break code, and have better predictability when it comes to their work More confidence from the developer’s side
- 15. Key benefits of BDD • In fact, BDD puts a great importance to the Business value & needs. By setting priorities with the client, based on the value it provides, developers are able to provide better result because they have a strong understanding of how the client thinks. By focusing on the value, no useless features are built. The software design follows business value • As mentioned earlier, the ubiquitous language is understandable by all the members of the team, which reduces misconceptions and misunderstanding and makes it easier for new members to join the working process. The ubiquitous language • By focusing on the business’ needs, you get satisfied users, and that implies a happy business of course. Actually with BDD, as its name says it, you focus on the behavior, which has a stronger impact than the implementation itself. Software development meets user need
- 16. Featues of BDD • Shifting from thinking in “tests” to thinking in “behavior” • Collaboration between Business stakeholders, Business Analysts, QA Team and developers • Ubiquitous language, it is easy to describe • Driven by Business Value • Extends Test Driven Development (TDD) by utilizing natural language that non technical stakeholders can understand • BDD frameworks such as Cucumber or JBehave are an enabler, acting a “bridge” between Business & Technical Language Assuming you’re building a web application, you’ll probably use a browser automation library like WatiR/WatiN or Selenium, and script it either using one of the frameworks I just mentioned, or a given/when/then tool such as Cucumber (for Ruby) or SpecFlow (for .NET).
- 17. The Rules When Writing BDD
- 18. BDD: - It is written as a plain English Text. - It is easy to understand by anybody because we write in Simple English Format. - It is a simple plain text format, BDD can be shared with Stakeholders. - Easy to learn and implement. BDD Tools Available in the Market: - Cucumber - Jbehave - Nbehave - Specflow => All the above tools are used different platforms and programming languages like Java, Ruby, CSharp, .Net etc. But all the above tools have one language is common which is know by “Gherkins Language”. Gherkin is the format of BDD tools. It is a plain English Text which is used to create scenarios. With the use of that, anybody can easily understand the software behavior. Gherkins have some specifically defined structure and few syntax which is used by the Automation Testers. The syntax is very easy and simple to use. Why BDD framework?
- 19. Example:
- 20. Step 1: Create Maven Project Create a new Maven project from scratch and add the following dependencies and plugins to the pom.xml file. Choose ‘Enable Auto-Import’ Maven projects prompt at the beginning (to manually enable this, go to File > Settings > search and select ‘Maven’ > choose ‘Importing’ > enable ‘Import Maven projects automatically’). Step 2: Add Cucumber for Java IntelliJ IDEA plugin: Go to File > Settings > Plugins > search ‘Cucumber for Java’> Install You may need to download dependencies of the plugin as well. If you are accessing the internet through a Proxy server, make sure you configure your IDE with proxy settings. Step 3: Project Directory Structure The directory structure of the sample project looks like the following. Note the structure of test features, step definitions, and the runner classes. Step 4: Create testng.xml Create testng.xml file in the project root and add below lines. Step 5: Build Maven Project Run the following command to build your project. How to apply BDD cucumber
- 21. - The choice between TDD and BDD is a complicated one. It depends on if there is an appropriate testing framework for your given target language, what your coworkers are comfortable with, and sometimes other factors. - Some argue that BDD is always better than TDD because it has the possibility of eliminating issues that might arise when using TDD. - The key to BDD is that it might prevent issues; it isn’t guaranteed to. Issues like poor code organization, bad design practices, etc. will still persist. You’ll just have a lower likely hood of writing bad tests and thus have more robust features. There is no essential difference between them. What holds them together is that they all require a group of people, specifying how the software should behave, collaboratively, before implementing it. That’s the important bit, so maybe that’s what we should boil the BDD definition down to. The idea is to work from the outside, thinking about how we want to pave, we use examples to make sure that everybody on the team understands what we’ve just agreed on – concrete examples with concrete data – and we write these examples in a ubiquitous language – a language using terms that derive from the business domain that are understood, unambiguously, by everybody on the team. conclusion III. TDD and BDD: differences and contradictions
- 22. • HTTPS://www.testingexcellence.com/bdd-guidelines-best-practices/ • http://compilehorrors.com/test-driven-development-tdd-vs-test-last-development-tld-a-comparative-study/ • https://en.wikipedia.org/wiki/test-driven_development • http://www.giorgiosironi.com/2010/03/tdd-checklist-red-green-refactor-in.html • https://apiumhub.com/tech-blog-barcelona/behavior-driven-development/ • http://b4usolution.com/tutorial/ Original Sources: IV. Demo for TDD and BDD
- 23. Please give some advise for our presentations!