During a panel discussion about Behaviour-Driven Development (BDD) at this year’s CukeUp 2015 conference Dan North came up with an idea of a community-curated resource for everyone interested in BDD with examples, adaptions, scenarios as well as experience reports and common practises and links to other external resources.
At Unruly teams have been applying eXtreme Programming (XP) since being founded in 2006. Teams take a test-first approach to developing code and invest in automated checks that can be run in live environments. InfoQ interviewed Rachel Davies about the importance of a continuous approach to testing, how this has evolved over the years and the business advantage that it delivers to Unruly.
Behavior driven development (BDD) can be used to improve communication between testers, developers and the business. For example you can use given-when-then scenarios to develop test scripts and at the same time define the requirements of the system. BDD involves all team members and helps them to think about the product.
The Spring Security team released Spring Security 4.0.0, adding several new features as well as more default security. Major themes include WebSocket Security, Spring Data integration, better testing support and the introduction of Spring Session as a new (Apache licensed) open source project.
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.
Behavior Driven Development (BDD) uses examples, preferably in conversations, to illustrate behavior. A lot of people focus on the tools if they are doing BDD but having the conversations is more important than writing down conversations and automating them said to Liz Keogh. An exploration of using BDD to do experiments to deal with complex problems and do discoveries.
DevOps Days Ljubljana 2015 took place on the 3rd and 4th April and talks covered the full CAMS spectrum: Culture, Automation, Measurement and Sharing.
With SmartBear Software recently announcing that they are assuming responsibility for the Swagger API open-source project, many companies involved in API development tools have wondered if there will be major changes. Questions are also coming from the open-source community and from professional API developers. InfoQ interviewed Tony Tam, founder of the Swagger project.
You can increase the quality of products by constantly increasing the level of automation of the delivery process and working with DevOps teams who constantly deliver small features to get quick customer feedback. A case story from ING Lease explaining the problems they had, experiences from the first steps of their agile and DevOps journey and exploring what they want to achieve in the future.
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.
Convinced that “whatever can be unit tested should be unit tested”, Mona El Mahdy, a Software Engineer in Test at Google, has written a blog post proposing several approaches to perform unit tests on the user interface of Android applications. Mahdy recommends Robolectric and the Android Studio Gradle plug-in for general unit testing, and Espresso or UI Automator for creating and running UI tests.
Here's an experience story from a tester who decided to move onward and become a Scrum master to help her team to become more agile, with learnings from their agile journey and pieces of advice for doing change in organizations.
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.
InfoQ did an interview with Gil Zilberfeld about managing the expectations that organizations have of agile and how to prevent misconceptions, valuable ideas and practices from agile and what the future will bring for agile.