Writing tests looks simple and every kid could write few lines of JUnit code. Writing valuable tests is more challenging. Everyone have seen (or written himself!) tests, which are hard to understand, hard to maintain, and do not verify anything really important (or maybe they do, but it is too hard to deduce)!
By working together to create the set of tests and then determining where that testing belongs, we can increase efficiency, reliability and reduce debugging time for failures in the future.
Now that a lot of software applications are directly visible from customers and that a failure has broader consequences, load testing has gained an increase importance in the software testing domain. In this Phd thesis, Zhen Ming Jiang propose an approache for the automated and systematic analysis of load testing logs.
Tools like Selenium make writing automated browser tests dead easy. Many teams never look further than this, and are satisfied with just replacing their laborious manual testing efforts with reliable Selenium scripts. They’ve missed a big opportunity.
This chapter from the “Hitchhiker’s Guide to Python” provides recommendations on how to perform unit tests in Python and presents the unitest and doctest modules. It also lists the tools that are available to perform unit testing in Python.
When discussing TDD with my friends and coworkers, often heatedly, an interesting pattern has appeared. All of the arguments about expensive refactoring and the need for up-front design are never really challenged. Instead, what has always been the final refuge for those arguing for TDD is that it makes development fun again.
HP Quick Test Professional is a test automation tool, also known as QTP. It is used to automate functional, regression and smoke test cases. It is a very popular software testing tool and works on MS windows O/S, supports development technologies like Active X, Delphi, Java, .Net, Oracle, People Soft, Web services etc. This article presents some best practices while doing automation using QTP.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates