Pride comes before a fall – A person who is extremely proud of his or her abilities will often suffer a setback or failure, because he or she tends to be overconfident and to make errors of judgment. Latching onto Agile as a weak guide can give people a false sense of security. Continue reading
Posted in BDD, coding, dsl, test automation, testing, Uncategorized
- Tagged BDD, development, environment, language, microsoft, Mink, programming, selenium
There is no reason you can’t use BDD for any programming environment. Here is slideshare presentation of PHPSpec, and BDD tool for PHP development.
Posted in BDD, exploratory testing
- Tagged BDD, development, environment, PHP, PHP development, PHPSpec, presentation, programming, programming environment, SlideShare, slideshare presentation
Another good pragmatic presentation on DSL (Doman-specific language), taking approach of extend existing programming languages and increasing readability.
Posted in BDD, coding, dsl, TDD
- Tagged cannot, Doman-specific, DSL, Extend, fashion, ideal, programming, readability
The gap between language-driven requirements and code is getting smaller, but for some reason it is taking us all a while to realise that programming languages have to become more readable. If you look a piece of any code, you will dereive things that you understand. If you remove all that you understand from the program and paste it in another doc, the chances are you will have (more of less) a description of what the code is doing, that you (and others) can understand.
Posted in ATDD, BDD, coding, dsl, TDD
- Tagged Call, development, DSL, fitnesse, Java, model, programming, test, while
What the biggest risk in development (leaving out frightening common omission of unit testing)? That what is written down as requirements suffers a chinese-whispers style path to code. TDD was an approach to address that risk, by saying that before functional coding starts as test based on requirement is derived, then functional coding done to pass the test. Oversimplifying the nuts and bolts, but that is general idea.
Posted in ATDD, BDD, coding, TDD
- Tagged agile, BDD, business, development, DSL, programming, risk, test, while
With rapid development comes need for rapid decisions – and as pre-emptive as possible!
[Spikes are] So-called because a spike is “end to end, but very thin”, like driving a spike all the way through a log.
Spike Described : Alaistair Cockburn