Posted on

Effective Java Application Testing With Cucumber and BDD

Increase your testing efficiency by utilizing Cucumber for Java application testing, fully integrated with Behavior-Driven Development (BDD). This guide provides comprehensive steps for project setup, scenario writing, step implementation, and reporting.

Introduction

Cucumber is a tool that supports Behavior-Driven Development (BDD). A good starting point in order to learn more about BDD and Cucumber, are the Cucumber guides. BDD itself was introduced by Dan North in 2006, you can read his blog introducing BDD. Cucumber, however, is a tool that supports BDD, this does not mean you are practicing BDD just by using Cucumber. The Cucumber myths is an interesting read in this regard.

Posted on

TDD, BDD, and ATDD

Software development is an iterative process that involves writing, testing, and refining code until it meets the requirements. Test-driven development (TDD), behavior-driven development (BDD), and acceptance test-driven development (ATDD) are three methodologies that support this process. TDD, BDD, and ATDD are all methodologies used in software development for testing and ensuring quality. While they all aim to improve software development quality, they differ in their approach and focus. This article will explore the differences between TDD, BDD, and ATDD.

Test-Driven Development (TDD)

Test-driven development (TDD) is a software development methodology focusing on writing tests before writing the code. It is an iterative process that involves writing a test, running the test, and then writing the code that passes the test. The goal of TDD is to write high-quality, maintainable code that meets the requirements and is free from bugs.

Posted on

30 Common CI/CD Interview Questions (With Answers)

Acing a CI/CD interview is all about preparation. Preparation starts with collecting as much information as you can about the prospective company, and their history, product, and interviewing process.

Next in the list is to brush up your technical skills because knowing your technical stuff will make you stand out. Questions (like the ones in this article) are a great way of testing your knowledge. To help you, we’ve collected and answered 30 common CI/CD interview questions. How many can you answer?

How Many of These Questions Can You Answer?

  1. What is version control?
  2. What is Git?
  3. What is a Git repository?
  4. Which other version control tools do you know of?
  5. What is a Git branch?
  6. What is merging?
  7. What is trunk-based development?
  8. What is Gitflow, and how does it compare to trunk-based development?
  9. How long should a branch live?
  10. What is continuous integration?
  11. How do CI and version control relate to one another?
  12. What’s the difference between continuous integration, continuous delivery, and continuous deployment?
  13. Name some benefits of CI/CD.
  14. What are the most important characteristics in a CI/CD platform?
  15. What is the build stage?
  16. What’s the difference between a hosted and a cloud-based CI/CD platform?
  17. How long should a build take?
  18. Is security important in CI/CD? What mechanisms are there to secure it?
  19. Can you name some deployment strategies?
  20. How does testing fit into CI?
  21. Should testing always be automated?
  22. Name a few types of tests used in software development.
  23. How many tests should a project have?
  24. What is a flaky test?
  25. What is TDD?
  26. What is the main difference between BDD and TDD?
  27. What is test coverage?
  28. Does test coverage need to be 100%?
  29. How can you optimize tests in CI?
  30. What’s the difference between end-to-end testing and acceptance testing?

Version Control

CI/CD interview questions may include version control and Git as a topic.

Posted on

What BDD Is and Why You Need It: Java and Behavior Driven Development

Is Behavior Driven Development Just Another Religion?

You might hear about BDD but still don't have a clear understanding of what it is. Here I'll try to simplify the main ideas and provide clear examples. This article is useful not only for developers but all people involved in the development process like analysts, product owners, and even guys from the business.

BDD Makes Application Logic More Transparent

Low Transparency in Application is a very known problem in IT. Quite often domain knowledge belongs only to the development team. As a consequence, to get even a simple answer you have to ask the developer to explain.

Posted on

A Guide to Cucumber Best Practices

In this post, we’ll share some good Cucumber practices, especially when writing scenarios using the Gherkin language, clarifying some BDD concepts and from these practices, how to build better scenarios.

BDD is a development strategy, and even if you do not follow this practice, we find it beneficial to use Cucumber (or a similar tool) since it "forces you" to document your automated tests before implementing them. It’s fundamental that these tests be made clear to a user who does not know the behavior of the described functionality and that they be maintainable to reduce the costs of making changes in the test steps.
This image by Cucumber reflects the idea of combining automated tests, having a living documentation, and at the same time, still having specifications that are executable. All of this is thanks to the approach of using a tool like Cucumber.