Try to keep units small, use appropriate tools, and pair-up programmers and tester; these are suggestions for writing good unit tests. Unit testing is a mixture of programming and testing; programmers can work together with testers to learn from each other and broaden their knowledge horizons.
The third and fourth days of the triple conference Better Software East / DevOps East / Agile Dev East held in Orlando, Florida, continued the trend established by the first two, with talks covering a wide range of topics but with a clear emphasis on testing. While days 1 and 2 were filled with half and full-day tutorials, days 3 and 4 were based on one-hour talks.
Between the 14th and 18th November, the three conferences Better Software East, DevOps East and Agile Dev East are taking place simultaneously in the same venue in Orlando, Florida. The conferences are organised around two days of tutorials, two days of talks, and a closing Agile Summit day with keynotes by several international speakers. InfoQ attended the conference to report on its contents.
Behaviour-Driven Development (BDD) can help in improving how business stakeholders and software developers communicate with each other, but there are some common anti-patterns when using Cucumber to run the automated tests, which Aslak Hellesøy, Matt Wynne and Steve Tooke described in a recent discussion.
Behaviour-Driven Development (BDD) recognizes that software development is fundamental to businesses of today and helps to improve how business stakeholders and software developers communicate with each other, Kevin Smith claims in a recent blog post about his experiences working with BDD.
Version 2 of the Behaviour-Driven Development (BDD) tool SpecFlow supports parallel test execution and adds support for xUnit 2.0 and NUnit 3.0. As well as an upgrade of all components to .Net 4.5 it’s also upgraded to the new Gherkin3 parser, now used across nearly all Cucumber tools.
An interview with Laurent Py about why decided to transition to agile and DevOps and the benefits that they are getting from that, the "testing swing", how you can measure behavior change to find out if a feature is valuable, on the strategy and approach for test automation and what he expects that the future will bring us in testing.
QASymphony has released qMap, a visual mapping solution for agile testers of cloud, mobile, big data and IoT apps. InfoQ did an interview with Kyle Cochran about why qMap was developed, how testers can use qMap to get insight into their testing results and manage testing and can use information from qMap improve the quality of their product, and how QMap can be deployed within agile and DevOps.
Remembering that automation is a side benefit and not the reason for BDD is one improvement to more closely follow the recommendations of BDD thought leaders, Joe Colantonio explains noticing six ways of improving work with a BDD mindset.
At the recent CukeUp 2015 conference an attempt was made to describe what Behaviour-Driven Development (BDD) actually is, and for Paul Rayner it was clear that BDD is a community centred on key values and principles still open to adding new practices, not a community focused on boundaries and exclusion.
Fran O'Hara's lessons learned integrating testing in agile teams, in particular ensuring required test competencies are in place. Full test integration in an agile team is not as simple as mixing a couple of testers in the team, instead multiple working practices and skills are needed for delivering quality applications in an agile world.
Cucumber was created as a way to overcome ambiguous requirements and misunderstandings, targeting both non-technical and technical members of a project team, but if you think Cucumber is a testing tool you are wrong, Aslak Hellesøy, who created Cucumber in 2008, recently stated. Julien Biezemans and Liz Keogh recently expressed similar opinions.
There is an evolution going on in testing. It used to be that testing was about confirming to the specification. Testers were often brought in too late and had too little influence, but that is changing now as Cirilio Wortel explained in his talk on the evolution of software testing.
Behaviour-Driven Development (BDD) is very much about conversations and examples but there is a software design part that can be used to bring BDD and Domain-Driven Design (DDD) practices together, combining the conversional bits with a domain-focused design activity, Konstantin Kudryashov explains in a presentation.
Behaviour-Driven Development (BDD) can help in overcoming the gap between the developer’s understanding of what needs to be built and the business’ understanding of the technical challenges caused by the requirements. The reason is improvement in communication between the two groups, Alistair Stead and Konstantin Kudryashov explains in their Beginner’s guide to BDD.