How to use BDD to unit test a compiler?
My team is writing a compiler for a domain-specific language (DSL) which will be integrated into an IDE. Right now, we are focused on the analysis phase of the compiler. We are not using any existing parser-generators (such as ANTLR) because we need real-time performance and highly detailed error/warning/message information. We have
How to use BDD to unit test a compiler?
My team is writing a compiler for a domain-specific language (DSL) which will be integrated into an IDE. Right now, we are focused on the analysis phase of the compiler. We are not using any existing parser-generators (such as ANTLR) because we need real-time performance and highly detailed error/warning/message information. We have
Jasmine BDD vs Integration Tests
Let’s say I need to write a test for the front end, in the following BDD style:
In BDD, going from feature to user story how does it works?
My background is the book BDD in action.
In BDD, going from feature to user story how does it works?
My background is the book BDD in action.
In the BDD paradigm why should the “ubiquitous language” be merely semi-formal and not completely formal?
Here’s the relevant quote:
In the BDD paradigm why should the “ubiquitous language” be merely semi-formal and not completely formal?
Here’s the relevant quote:
In the BDD paradigm why should the “ubiquitous language” be merely semi-formal and not completely formal?
Here’s the relevant quote:
In the BDD paradigm why should the “ubiquitous language” be merely semi-formal and not completely formal?
Here’s the relevant quote:
BDD/TDD – exhaustively testing details which are low-level, but still behaviour
We’re looking to concentrate more on testing behaviour (as opposed to every class/method individually) in all our automated tests, as espoused by various high-profile online discussions recently. I like the idea of thinking about only what goes in and out of certain logical well-defined boundaries between components, but I’m having a hard time imagining how that relates to quite low-level detail of behaviour, that is only a small part of the overall requirement but still important to be correct.