Unit Tests are ultimately a way to ensure quality by catching defined errors cases early. There exist many handy and excellent tools for unit testing, and even methodologies like Test Driven Design based around unit tests. As a result of this, developers tend to use unit tests “for everything”, and consequently use the term too broadly.
Distributed software development teams and distributed software testing are here to stay. In this article, Lisa Crispin asks “How do we get quality software in these situations?” and proposes some hints on how to get good results when you perform software testing with distributed teams.
Venus.js in an open source software testing tool developed by LinkedIn that allows you to organize and run your entire JS testing system with a single tool using Node.js. Venus eliminates repetitive tasks and friction points and lets you focus on writing tests instead of running them.
eBay’s European quality engineering team has broad experience implementing end-to-end test automation in different software development environments (agile, waterfall, co located , outsourced, distributed). This presentation illustrates the key lessons learned from a technical and business perspective.
Automating tests is an investment that is valuable as long as the investment is not too great. As such investing in automated testing tools can be great or bad depending on if your company really needs to automate. We want to get to the payback more quickly. The true investment is not only the cost of creating and maintaining automated tests. Watir is a family of libraries for testing web applications. Watir reduces the cost of creating automated tests that are maintainable. If we spend too much time fixing and debugging, we will never get the new features created, or we will abandon the automated tests temporarily.
One of the biggest challenges in writing test automation scripts comes in keeping pace with the rapid changes of the application under test. One small “critical” change made by a dev at midnight can result in hours of painful investigation and test script repair for you the next morning(s).
When you need to perform unit testing in an independent way, you use mock objects. Mock objects are simulated objects that mimic the behavior of real objects in controlled ways. In this excerpt of their book “Pragmatic Unit Testing in C# with NUnit”, Andy Hunt, Dave Thomas and Matt Hargett explain how to avoid coupling when you build your C# unit tests.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates