BT

InfoQ Homepage TDD Content on InfoQ

  • So, How Do You Make Agile Successful?

    It is not Agile's fault, it is your fault - Are you fed up with such statements? This article tries to provide a more constructive answer on how to make Agile successful. It first shows how Scrum can be harmful, then argues how Agile requires different skills on both product and delivery levels. It suggests to use CICD to counteract Scrum's traps and stresses the importance of systems thinking.

  • Beyond Page Objects: Next Generation Test Automation with Serenity and the Screenplay Pattern

    Automated acceptance testing reduces time wasted in manual testing and bug fixing, and when combined with Behaviour-Driven Development, can guide development effort. But it requires skill, practice and discipline. The Screenplay Pattern helps teams address these difficulties and is where you may end up by mercilessly refactoring Page Objects using SOLID design principles.

  • Testers in TDD teams

    In a team doing TDD (Test Driven Development) there is no need for testers that do manual checking. For testers this means that much of their traditional work disappears. Meanwhile modern testing solutions have become so technical that implementation requires specialists. For testers this presents a very interesting opportunity, but it requires solid technical skills.

  • A Conversation with James Shore on Agile Fluency and Let's Code Javascript

    At the recent Agile Australia Conference James Shore gave a keynote talk and a workshop on Agile fluency. He spoke to InfoQ about his work on agile fluency, teaching and building tools for test driven development in javascript.

  • Q&A on Test Driven Development and Code Smells with James Grenning

    InfoQ interviewed James Grenning about why people are not doing technical practices sufficiently or well enough, why he thinks that TDD can be fun, the importance of unit tests, why programmers need to have a good nose for code smells and how they can become better in discovering "bad code”.

  • Why We Fail to Change: Understanding Practices, Principles, and Values Is a Solution

    There’s no reward for being a Scrum or kanban shop if we are not delivering value to customers. We see virtually no impact of agile or lean on the bottom line of success rates of improvement initiatives, because organizations often look for recipes. We need to change our mindset, and focus on the principles that people follow and values they share and the bigger whole: organizational culture.

  • Interview and Book Review: BDD In Action

    "BDD In Action" is a book that aims to cover the full spectrum of BDD practices from requirements through to the development of production code backed by executable specifications and automated tests.

  • Refactoring Coderetreats: In Search of Simple Design

    In cities all over the world, groups of software developers have been getting together at weekends repeatedly trying to write code for a given problem, but never completing a solution. At coderetreats, developers learn from each other and refine their software design skills. In this article David examines how they work? What do people say about them? How to make them even better?

  • Yes, Hardware Can Be Agile!

    “You can’t do 2-week iterations with hardware!” This is the first thing you’ll hear when talk turns to Agile methods in hardware-software product development. A mix of existing robust hardware development ideas, plus a few newly taken from Agile software are being used now by real teams, even to get around - or through - the challenge of doing fast iterations.

  • James Grenning on Technical Excellence

    At then recent Agile Singapore conference James Grenning presented two technically focused talks - one on the importance of technical excellence and the other teaching test driven development. He spoke to InfoQ about the importance of strong technical practices to enable true agility in software development.

  • Q&A about the book Common System and Software Testing Pitfalls

    The book Common System and Software Testing Pitfalls by Donald Firesmith provides descriptions of 92 pitfalls that make testing less efficient and effective. The descriptions explain what testers and stakeholders can do to avoid falling into the pitfalls and how to deal with the consequences when they have fallen into them.

  • The Life and Times of TDD

    Scott Ambler discusses a recent mini-survey designed to find out how TDD is being used in practice. He examines the state of practice and what techniques and tools are being used with TDD.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.