Agile Thoughts

Agile Thoughts - A podcast about Agility and Modernity · agilenoir.biz · American English

A podcast about Agility and Modernity

rss2 wordpress content slash wfw atom dc sy

Open the feed

https://agilenoir.biz/en/feed/

Last post: Apr 12, 2017
Posts in 24 h · 7 days · 30 days: 0 · 0 · 0
Our last check: Answering
Served from: United States
Site title: Agile Thoughts podcast
Text score at discovery: 14,072
Format: rss2
Features in the feed: content, slash, wfw, atom, dc, sy
Community: wordpress

Posts

What our queue read from this feed. Open one to read it here, or go to the site that published it.

Getting Service APIs to Behave using BDD & SoapUI
Apr 12, 2017 · original
For this example we’ll use CucumberJVM (AKA Cucumber for Java, here and here are install documents). SoapUI (part of the ReadyAPI suite) is a powerful tool for testing SOAP or REST endpoints. SoapUI isn’t a BDD tool but for teams who like to use SoapUI for creating system tests, with some adjustment they can drive their SoapUI tests with a BDD framework. This allows SoapUI tests to be linked to features because we build software to create features, not to build APIs (dogs should wag tails after all, not the other way around). Although there are other alternatives achieving this without SoapUI, for teams committed to using SoapUI, here is how to combine the use of a BDD tool (Cucumber in this case) with SoapUI. This article takes you through the recipe of making Cucumber and SoapUI work together. It’s not necessary to use my source code but if you find it helpful, the code for a test proj
BDD and Exo-Testing For Upstream Dependency Headaches
Mar 7, 2017 · original
Although SOAPUI and BDD can be complimentary, when adding BDD test automation into existing test processes that use SOAPUI, it can be confusing how to adjust the manner these tools are used. Once a team uses BDD in lieu of imperative specifications (traditional requirements that describe how to build the software) they are already using BDD scenarios for describing the behavior they want from the software solution. But now what to do about test automation? Functional Testing Continue using SOAP UI will result in tests and test reports with no linkage between the BDD scenarios used for planning and test results. This means feature documentation in the form of BDD scenarios will go out of date. In summary, BDD will give the team value by reducing or eliminating requirements misses but won’t result in maintained documentation. Conundrum If the intent of the SOAPUI tests is to prove the func
Dial the Focus on Behavior
Dec 20, 2016 · original
How detailed should BDD scenarios get? BDD is a powerful requirements analysis tool that first establishes what the business wants before deciding *how* to solve the problem. Here is how to use this macro scopic tool for requirements analysis. Let’s say the PO brings this user story to a team. As a writer I want a spelling checker So that I can correct my spelling mistakes With our user story specified, lets add acceptance criteria in the form of BDD scenarios: Scenario: dog spelled incorrectly Given When spell checking Then suggest d and g and dog Examples: |missing one letter| |dg | |og | And so we keep going: Scenario: cat spelled incorrectly .... HOLD ON! We’re going to end up writing examples for the entire English dictionary at this rate, which means around 1 million scenarios for an unabridged dictionary. too detailed? Let’s ask some questions: Is this a novel new feature? Or does
Am I BEHAVIORAL or NOT?
Dec 12, 2013 · original
Behavioral Driven Development (BDD) provides a communication mechanism across all the roles required for requirements and software development (customers, managers, marketing, analysts, development, test, architects, release management). Since BDD scenarios are expressed in the language of the user, the practice of using scenarios across all those roles gets people familiar with how users get work done , and talking to each other (regardless of role) in this language. Also, these BDD scenarios can drive automated tests to provide pass or fail status on what behaviors are in the software. Because these behaviors are written in the language of the user, the tests “talk to us” by being “live” documentation that express how the software is working. Why BEHAVIORAL? Software engineering requires coordination of groups of people with different roles and likely from different organizations. Doin
Behavior Driven Development (BDD)
Dec 6, 2013 · original
Behavior Driven Development is a requirements communication strategy which as a side affect, prepares for system test automation similar to Acceptance Test Driven Development (ATDD). Requirements are expressed by the PO as sets of scenarios, commonly implemented using the keywords of Given, When, Then. This white paper describes the work I did in helping a Fortune 50 company roll out BDD across a multisite enterprise of 2-3,000 developers. WANT TO LEARN MORE? I’m putting together a BDD training series, some of it is free such as podcasts, videos, and blog articles like this one sent straight to your email box, and some of it is for a small fee for books and online training products. Go here to opt in to receive periodic emails. Otherwise, enjoy the site. The post Behavior Driven Development (BDD) first appeared on Agile Thoughts .
Find help
Dec 5, 2013 · original
As a consultant, technical lead, and Agile coach, I work with teams and organizations to realize their potential through my fifteen years of experience in technical Agile practices and management by getting people focused on fixing what’s holding them back. I also help them through training, facilitating collaborative planning meetings, and delivering code and mentorship via pair programming. I regularly travel and consult with clients in China, India, and the United States, and I speak poor but workable Mandarin. If you want advice or talk over your situation, contact me and I’d be happy to discuss what’s on your mind. Otherwise, enjoy the site: Learn, read, have fun! Lance Kind 康美国 CSM, Agile Coach, Agile Developer email: LancerKind@gmail.com N. America Phone: +01 208 964 0837 China: +86 1866926591 Twitter: @LancerKind 新浪微博:@康美国 The post Find help first appeared on Agile Thoughts .
Agile Noir, the novel
Dec 5, 2013 · original
Book cover of the English editions of Agile Noir There are lots of books about Agile software development which state clearly the problems of traditional development and how Agile software development will improve the ability to deliver software. But still, not everyone is doing it yet. Part of the problem is that it’s hard for companies to change their culture to something as groundbreaking as Agile. (If you don’t understand this, then you are either working at a near Agile company, or you don’t understand how Agile is different from traditional Waterfall process and their divide and conquer patterns.) Another part of the problem is well, maybe reading the books aren’t enjoyable. And additionally, there isn’t enough context around the process talk to ground the practices into your reality. Enter the business novel Business novels take a different approach to conveying information. Rathe

Discovered by the rss-feed-index crawler, which checks each feed at most once a month.

Same record as JSON: https://api.agentalog.com/api/feeds/fd_agilenoir_biz_7bc7513b3343b903. More from this site: agilenoir.biz in the Feeds tab.