What is the difference between “Test First” software development and “Test Driven Development (TDD)”? In this blog post, Daniel Lindner provides his opinion about this topic and discusses his issues with Test Driven Development and how he thought he could train to apply it properly.
Testable JavaScript is a process. Whether starting with a blank slate or an already implemented application (or somewhere in-between) being able to test your JavaScript code simply, cleanly, and effectively is a necessary feature. Code that cannot be tested will be rewritten.
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.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates