Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
This article explores how Gorilla Logic's new, open source Flex user interface automation testing tool, FlexMonkey, can enhance the productivity of both developers and QA testers. FlexMonkey allows developers to incorporate user interface testing into unit test suites and continuous integration environments, and allows QA testers to expand those tests into comprehensive quality tests.
It is often the case, a new piece of software is developed by someone who needed to fill a void left by an existing product. Software evolves from tools we use which don't exactly meet our needs, this is the case with a new Behavior Driven Development (BDD) tool called Coulda, developed by Evan Light.
Devver is a new service that runs your Ruby tests in parallel on their cloud infrastructure. InfoQ talked to Ben Brinckerhoff from Devver to understand how they can speed up your tests.
This article is a crash course in writing maintainable JavaScript. We'll add features to a running example by iteratively following a simple principle: write a unit test, make it pass. Each test will serve as a quality feedback loop, creating both a safety net and an executable form of documentation for anyone who wants to change the production code.
In this interview with Eli Lopian of Typemock, he discusses the impetus for Typemock, it's differentiators and program futures. Typemock was originally created to fill a need for a Test Driven Development tool within the .NET community.
We're charged with the task of writing software that is reliable, sturdy, and trustworthy. We could all write tests and extensive preconditions for our code, and choose languages which make errors less likely, but across the industry we don't do any of these things uniformly. Michael Feathers looks at error-prevention in the short history of our discipline and considers our possible futures.
Writing a test makes you clarify your ideas about what needs to be done, and making the test pass means that you know that you've added a little more functionality today. Having a comprehensive suite of tests gives you the confidence to get on with things because you can tell when you've broken the system, and tests that are difficult to write show you where you need to improve.
Brian Marick discusses what he means by micro-scale-retro-futurist-anachro-syndicalism and why we should go back to the roots of Agile. He talks about what he thinks were the mistakes in the Agile Manifesto, how it has lead to the state of the Agile community today, and how we can build better systems by making them so that they are much more easily tested.
In this interview from QCon London 2008, Erich Gamma discusses the Jazz project, why Eclipse has been successful, the strict Eclipse release schedule, JUnit, Design Patterns, how to identify a design pattern, design patterns and the 'Don't Repeat Yourself' principle, the design pattern community, and whether dependency injection is a design pattern.
This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them. Business values are also a component of these patterns so your adoption is always focused on addressing your particular environment.
