System Under Specification, SUS

Filed under: BDD, — Tags: SUS, SUT — Thomas Sundberg — 2013-10-15

Ian Kelly called the System Under Test, SUT, the System Under Specification, SUS, at his session “Testing++ – Working with Spock and Geb” on Java Developer Day in Krakow.

System under upecification feels quit nice in the context of Behaviour Driven Development, BDD, where you define what the system should do and not how it should be done. I usually talk about system under test but I think I will change that. Or at least mix what I use. I want to emphasise that a test should be more of a specification than a verification. The word specification also emphasises the order in which things should be done. You usually specify what you want first. You don’t specify afterwards what you got.

Creating a specification after you delivered the software is documenting what actually was delivered and nothing else.

Resources



(less...)

Pages

About
Events
Why

Categories

Agile
Automation
BDD
Clean code
Continuous delivery
Continuous deployment
Continuous integration
Cucumber
Culture
Design
Executable specification
Gradle
Guice
J2EE
JUnit
Java
Linux
Load testing
Maven
Mockito
Pair programming
PicoContainer
Programming
Public speaking
Quality
Recruiting
Requirements
Scala
Selenium
Software craftsmanship
Software development
Spring
TDD
Teaching
Technical debt
Test automation
Tools
Web
Windows
eXtreme Programming

Authors

Thomas Sundberg
Adrian Bolboaca

Archives

Meta

rss RSS