Content tagged as 'Atdd'

Here is a list of all the content that has been tagged as (Acceptance Test Driven Development) atdd.

Checkout one of Kim’s previous talks on the topic.

Holistic Info-Sec for Web Developers

A three part book series focused on lifting the security knowledge of Software Developers, Engineers, and their teams, so that they can continuously deliver secure technical solutions on time and within budget, without nasty surprises.

Workshop - Security Regression Testing with ZapAPI and NodeGoat

At AWS Auckland, Kim will demonstrate the OWASP Zap API with NodeGoat, which helps you identify vulnerabilities in your web application as you create it, rather than at the end of a project.

Workshop - Security Regression Testing with ZapAPI and NodeGoat

NodeJS Auckland: Kim will demonstrate the OWASP Zap API with NodeGoat, which helps you identify vulnerabilities in your web application as you create it, rather than at the end of a project.

Workshop - Security Regression Testing with ZapAPI and NodeGoat

This time in Kilkenny of Ireland, Kim will demonstrate the OWASP Zap API with NodeGoat, which helps you identify vulnerabilities in your web application as you create it, rather than at the end of a project.

Workshop - Security Regression Testing with ZapAPI and NodeGoat

This time in New York City at OWASP, Kim will demonstrate the OWASP Zap API with NodeGoat, which helps you identify vulnerabilities in your web application as you create it, rather than at the end of a project.

Workshop - Security Regression Testing with ZapAPI and NodeGoat

Kim will demonstrate the OWASP Zap API with NodeGoat at the meetup he usually facilitates, which helps you identify vulnerabilities in your web application as you create it, rather than at the end of a project.

Workshop - Security Regression Testing with ZapAPI and NodeGoat

At CHC.js Kim will demonstrate the OWASP Zap API with NodeGoat, which helps you identify vulnerabilities in your web application as you create it, rather than at the end of a project.

Automating Specification by Example for .NET Web Applications

Redirects to legacy blog post.

It’s my intention that the following details will help you create a system that automates “Specification by Example”.

Talk - Moving to test and behaviour-driven development

At Canterbury Software Cluster: In this session Kim went over the benefits of introducing TDD and BDD: How to introduce them, their differences, how to deal with push back from team members and upper management.

Moving to TDD

Redirects to legacy blog post.

The first thing to clear up is that TDD is not primarily about testing, but rather it forces the developer to write code that is testable (the fact the code has tests written for it and running regularly is a side effect, albeit a very positive one).