Functional testing and Acceptance testing leading to redundant code
What I know is:
Is BDD scalable for medium to large projects?
In every Website you read about BDD (Behaviour Driven Development) you find a very simple nice example showing you how obvious and easy is it to define your requirements. But trying to implement this process in a big product (not a calculator example) showed me that things can get (or will get) pretty complex and unreadable; especially changing requests at a later point means a lot of work to correct the Integration tests for this.
Is there a reason that tests aren’t written inline with the code that they test?
I’ve been reading a bit about Literate Programming recently, and it got me thinking… Well-written tests, especially BDD-style specs can do a better job at explaining what code does than prose does, and have the big advantage of verifying their own accuracy.
How to develop a Delete command through Behavior Driven Development?
I am trying to develop a Delete command through BDD that will simply delete an user from the database, given user_id as a parameter. What can be some possible behavioral tests that will drive me to write a proper implementation for the command?
Should I use TDD and BDD if my project is changing fast?
I have my own little project I am creating using RoR, I plan it to have small-medium load.
With no doubt I started with BDD and TDD (Cucumber and RSpec to be exact, but I am also experienced with TestUnit), I like it but since it’s my own project and it’s a somewhat startup – I am changing many things in it, many requirements, many ideas how things should work and look. So it becomes too much time-consuming to always code it using BDD and TDD, even if I cover only common cases.
What should I do? Should I sacrifice BDD and TDD for productivity till I get to some point when I have a solid basis and it’s time for production, and than I write tests?
Should I write them right now but as minimal as possible? Should I only write RSpec and forget about Cucumber for now? Or maybe just TestUnit to test model for now since it’s the most important and everything else can change?
Thanks in advance!
BDD and behavior based on complex state
I’m wondering how to write BDD test cases for a real system. All examples I can find are trivial and do not answer the question.
What are examples of automating BDD specifications through the UI layer?
I understand it is better to automate BDD specifications below the user interface whenever possible.
What are examples of automating BDD specifications through the UI layer?
I understand it is better to automate BDD specifications below the user interface whenever possible.
What are examples of automating BDD specifications through the UI layer?
I understand it is better to automate BDD specifications below the user interface whenever possible.
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