This presentation incrementally demonstrates the concepts of Unit Testing, Test-Driven Development (TDD) and then Behavior-Driven Development (BDD) that enable us not just to create robust regression tests, but also clean and maintainable code.
It’s 4am and you don’t know it, but you’re about to get three times the traffic you were expecting. Is your service ready to handle it? Systems are only as scalable as their weakest component. Large scale load testing in production is the best (and surest) way to ensure that services can truly scale to the unexpected and Amazon Web Services (AWS) can help you.
Software testing code is like programming code: it can be useful in the long term only if it is maintainable. In this article, Mehdi Khalili shares some tricks on how to build a maintainable suite of automated test cases.
Software testing during the transition to Agile, particularly if you’re moving from a classic waterfall system, is not easy. This part discusses how to perform software testing when you don’t have the classical workflow of documented test cases and bug requests than in a traditional approach.
Tests are supposed to save us money. How is it, then, that many times they become millstones around our necks, gradually morphing into fragile, breakable things that raise the cost of change? We write too many tests and we test the wrong kinds of things.
This article from Alan Bowers and James Bell provides an introduction to setting up a software testing infrastructure using Selenium WebDriver and Cucumber. It shows how to create a test suite for single-page web applications and to run tests across multiple web and mobile browsers via Selenium Grid.
Software testing is a good thing, right? But how much should we test? What’s not enough? What’s too much? What should we test, and when? This talk looks at the many levels of testing, from the outermost UI tests to unit tests, what works well, what doesn’t work well.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates