Learn how to improve your software testing strategies, with theoretical ideas, practical tips and examples. A good test strategy drives your testing effort towards the testing mission, and is specific, anchored, pragmatic, effective and possible to change.
How do you perform software testing in a continuous deployment environment where you have more than 10 releases a day? How can you be confident that the code running in production is still reliable? In this blog post, Andy Hume explains the software quality process the Guardian uses for continuous deployment mode.
A Reflection on Up-Front Testing As we were saying, up-front testing really isn’t testing at all. It is really up-front design through the analysis of our tests. Can we take this testing even further? When XP came out and suggested doing unit tests, many of us realized that if we combined a series of unit tests together, we could get the equivalent of automated acceptance testing.
Learn the best practices for testing mobile applications on smartphones and tablets. This video discusses the challenges of testing mobile applications, knowing the application you are testing, the different types of mobile testing, the tools and resources that could help your mobile testing efforts.
Test-Driven Development (TDD) is one of the main technical practice of agile software development. In his blog post, Bradley Braithwaite shared the top five Test-Driven Development mistakes based on his own experience as a consultant. These mistakes lead organizations to abandon TDD because they think that there is no return on the time invested in Test-Driven Development or the code base become more difficult to maintain.
Test Driven Development (TDD) is a powerful tool to produce quality code, but if it is not used correctly it can also put your project in a difficult position if it is not used correctly. In this article, Jakub Nabrdalik explains that TDD is simple to learn, but hard to master. He shares some tips on how to avoid Test Driven Development traps.
What main factors contribute to success in test automation? What common factors most often lead to the failure of an automation effort? There are no simple universal answers to these questions, but some common elements exist. We believe that two of the most important elements are management issues and the testware architecture:
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates