Testing and Debugging Main
Articles:
- Writing a Simple Automated Test in FitNesse by Jeff Langr - [Clicks: 38]
Here is your chance to test a web application, a web services API, a desktop UI, or something else.
http://www.developer.com/design/article.php/3649506 - Dec, 2006 - Using JMock in Test Driven Development by Paulo Caroli - [Clicks: 34]
Applying Mock objects effectively is a key factor when performing Test Driven Development (TDD). In this article I'll introduce the basics of using JMock, a Mock object framework, in conjunction with Test-Driven Development. To illustrate the technique I will work through a case study, the creation of a cache component by means of test-first development with JMock.
http://www.theserverside.com/tt/articles/article.tss?l=JMockTestDrivenDev - Dec, 2006 - Moving Forward with Automated Acceptance Testing by Jeff Langr - [Clicks: 16]
Download a tool to help you set up automated acceptance testing for your team. You will also install it, start it up, and begin to learn about its editing capabilities.
http://www.developer.com/tech/article.php/3646711 - Dec, 2006 - In pursuit of code quality: Performance testing with JUnitPerf by Andrew Glover - [Clicks: 30]
Performance testing is usually left for last in the application development cycle -- not because it's unimportant, but because it's hard to test effectively with so many unknown variables. In this month's In pursuit of code quality, Andrew Glover makes the case for performance testing as part of the development cycle and shows you two easy ways to do it.
http://www.ibm.com/developerworks/java/library/j-cq11296.html - Nov, 2006 - The Need for Automated Acceptance Testing by Jeff Langr - [Clicks: 15]
How would you like to automate some of your testing. See how that is possible.
http://www.developer.com/tech/article.php/3643611 - Nov, 2006 - In pursuit of code quality: Use test categorization for agile builds by Andrew Glover - [Clicks: 10]
Everyone agrees that developer testing is important, but why is it so darn time consuming to run tests? This month, Andrew Glover reveals the three categories of testing needed to ensure end-to-end system soundness and then shows you how to automatically sort and run tests by category. The result is a dramatically reduced built time, even with today's massive test suites.
http://www-128.ibm.com/developerworks/java/library/j-cq10316/index.html - Oct, 2006 - Fuzz testing by Elliotte Harold - [Clicks: 11]
Fuzz testing is a simple technique that can have a profound effect on your code quality. In this article, Elliotte Rusty Harold shows what happens when he deliberately injects random bad data into an application to see what breaks. He also explains how to use defensive coding techniques such as checksums, XML data storage, and code verification to harden your programs against random data. He concludes with an exercise in thinking like a code cracker -- a crucial technique for defending your code.
http://www-128.ibm.com/developerworks/java/library/j-fuzztest.html - Sep, 2006 - In pursuit of code quality: Repeatable system tests by Andrew Glover - [Clicks: 6]
Writing logically repeatable tests is especially tricky when testing Web applications that incorporate a servlet container. In his continued quest to improve code quality, Andrew Glover introduces Cargo, an open source framework that automates container management in a generic fashion, so you can write logically repeatable system tests every time.
http://www-128.ibm.com/developerworks/java/library/j-cq09266.html - Sep, 2006 - Testing Concurrent Programs by Brian Goetz - [Clicks: 22]
In this article, Brian Goetz, author of the recently-released Java Concurrency in Practice, explores some of the major issues in testing concurrent classes, and offers some techniques for constructing concurrent programs that make them easier to test.
http://www.theserverside.com/tt/articles/article.tss?l=TestingConcurrent - Sep, 2006 - Java theory and practice: Testing with leverage, Part 3 by Brian Goetz - [Clicks: 8]
The first two installments in this series showed how static analysis tools like FindBugs can provide greater leverage in managing software quality by focusing on entire categories of bugs rather than on specific bug instances. In this final installment on testing, Brian Goetz examines another technique for smoking out bugs that violate design rules: aspects.
http://www.ibm.com/developerworks/java/library/j-jtp08226.html - Aug, 2006 - Code Reviews by Srivaths Sankaran - [Clicks: 23]
Need to be sure your program really runs right? Oh sure, testing's a part of it, but so are code reviews. Sri Sankaran argues that research and experience prove that a standardized, effective code review process mitigates costs and produces better code.
http://today.java.net/pub/a/today/2006/08/17/code-reviews.html - Aug, 2006 - Automation for the people: Continuous Inspection by Paul Duvall - [Clicks: 19]
When starting new projects, most of us plan to review code before actually releasing it into production; however, when delivery schedules supersede other factors, reviews tend to be the first practice thrown out. What if you were able to perform a portion of these reviews automatically? In this first article of the new series Automation for the people, development automation expert Paul Duvall begins with a look at how automated inspectors like CheckStyle, JavaNCSS, and CPD enhance the development process and when you should use them.
[Includes sample code]
http://www-128.ibm.com/developerworks/java/library/j-ap08016/index.html - Aug, 2006 - Hand-rolled mocks made easy by Gary Tong - [Clicks: 11]
Unit testing is something we all need to do, but getting good code coverage can be a daunting task. In this article, Gary Tong focuses on one of the basic elements of unit tests: mock objects. Using a hybrid static/dynamic approach, he shows how flexible, useful mock objects can be written in a matter of minutes.
http://www.javaworld.com/javaworld/jw-07-2006/jw-0731-mock.html - Jul, 2006 - Java theory and practice: Testing with leverage, Part 2 by Brian Goetz - [Clicks: 6]
June's Java theory and practice column demonstrated how static analysis tools like FindBugs can bring greater leverage to bear on managing software quality by focusing on entire categories of bugs rather than on specific bug instances. In this month's installment, resident exterminator Brian Goetz details the process of constructing and tuning a nontrivial bug pattern detector.
http://www-128.ibm.com/developerworks/java/library/j-jtp07256.html - Jul, 2006 - Role of Testing in Agile Projects by Jon Kern - [Clicks: 11]
According to Jon Kern, the difficulty with "agile development" and "testing" is that they can both be "in the eye of the beholder." This article outlines the different roles that various tests can play in agile development.
http://www.theserverside.com/tt/articles/article.tss?l=TestingAgile - Jul, 2006 - In pursuit of code quality: Tame the chatterbox by Andrew Glover - [Clicks: 23]
Just seeing a sprawling code block from a distance gives some developers the willies -- and it should! Loquacious code is often the hallmark of complexity, which results in code that is hard to test and maintain. This month, learn three important ways to measure code complexity, based on method length, class length, and intra-class coupling. In this installment of In pursuit of code quality, quality expert Andrew Glover starts out with tips for eyeballing code excess, then shows you how to use tools like PMD and JavaNCSS for more precision when you need it.
http://www-128.ibm.com/developerworks/java/library/j-cq06306/index.html - Jun, 2006 - Getting Started with EasyMock2 by Ralf Stuckert - [Clicks: 30]
One impediment to test-first development is object inter-relationships that are hard to recreate outside of their runtime container. EasyMock is one approach to creating "mock objects" to provide the parts of the system that aren't available at test time. Ralf Stuckert shows you how the latest version of EasyMock uses Java SE 5.0 features to simplify testing.
http://today.java.net/pub/a/today/2006/06/20/getting-started-with-easymock-2.html - Jun, 2006 - Java theory and practice: Testing with leverage, Part 1 by Brian Goetz - [Clicks: 8]
Back in June 2004, veteran exterminator Brian Goetz introduced the FindBugs static code analysis tool, which can detect bugs even in well-tested software. This month, he revisits that topic and looks at how static analysis tools can change the way you manage software quality by aiming development resources at entire classes of bugs rather than specific instances.
[Includes sample code]
http://www-128.ibm.com/developerworks/java/library/j-jtp06206.html - Jun, 2006 - Testing object serialization by Elliotte Harold - [Clicks: 26]
Even great developers sometimes forget to test object serialization, but that doesn't excuse you from making the same mistake. In this article, Elliotte Rusty Harold explains the importance of unit testing object serialization and leaves you with some tests to remember.
http://www-128.ibm.com/developerworks/java/library/j-serialtest.html - Jun, 2006 - Fit for analysts and developers by Narayanan Jayaratchagan - [Clicks: 15]
Do you think automated user acceptance testing is a cool idea, but impossible or not worth doing? Have you been bogged down by the traditional record/script/replay approaches and unable to automate until the code is complete? This article will show you how the Framework for Integrated Test (Fit) makes it easy to overcome these challenges and practice test-first design from the user perspective.
[Includes source code]
http://www.javaworld.com/javaworld/jw-06-2006/jw-0612-fit.html - Jun, 2006 - In pursuit of code quality: Refactoring with code metrics by Andrew Glover - [Clicks: 12]
In earlier installments of In pursuit of code quality, you learned how to use code metrics to objectively measure code quality. This month, Andrew Glover shows you how to use those same metrics and the Extract Method pattern for targeted refactoring.
http://www-128.ibm.com/developerworks/java/library/j-cq05306/index.html - May, 2006 - In pursuit of code quality: Code quality for software architects by Andrew Glover - [Clicks: 13]
Most well-designed software architectures are intended to support a system's extensibility, maintainability, and reliability. Unfortunately, inattention to quality issues can easily undermine a software architect's best effort. In this installment of In pursuit of code quality, quality expert Andrew Glover explains how to continuously monitor and correct quality aspects of code that can affect the long-term viability of your software architecture.
http://www-128.ibm.com/developerworks/java/library/j-cq04256/index.html - Apr, 2006 - Multithreaded unit testing with ConTest by Yarden Nir-Buchbinder, Shmuel Ur - [Clicks: 28]
Concurrent programming is notoriously bug-prone. Worse, concurrent bugs tend to be detected late in the development process when they cause considerable damage and are hard to debug. Even when they are done thoroughly, conventional unit-testing practices are likely to miss concurrent bugs. In this article, concurrency experts Shmuel Ur and Yarden Nir-Buchbinder explain why concurrent bugs are so hard to catch and present a new solution from IBM Research.
[Includes sample code]
http://www-128.ibm.com/developerworks/java/library/j-contest.html - Apr, 2006 - In pursuit of code quality: Monitoring cyclomatic complexity by Andrew Glover - [Clicks: 23]
If complexity has been shown to correlate to defects, doesn't it make sense to monitor your code base's complexity values? Andrew Glover shows you how to use simple code metrics and Java-based tools to monitor cyclomatic complexity.
http://www-128.ibm.com/developerworks/java/library/j-cq03316/index.html - Mar, 2006 - Test-first development with FitNesse by Stephan Wiesner - [Clicks: 40]
This article describes how the open source wiki FitNesse can be used to implement a real test-first development process by bringing customer, requirements engineer, developer, and tester together. Requirements get more precise, change is minimal, and test data is removed from the JUnit tests, making them much cleaner and easier to maintain.
http://www.javaworld.com/javaworld/jw-02-2006/jw-0220-fitnesse.html - Feb, 2006 - In pursuit of code quality: Don't be fooled by the coverage report by Andrew Glover - [Clicks: 11]
Test coverage tools bring valuable depth to unit testing, but they're often misused. This month, Andrew Glover brings his considerable expertise in this area to his new series, In pursuit of code quality. This first installment takes a closer look at what the numbers on the coverage report really mean, as well as what they don't. He then suggests three ways you can use your coverage to ensure code quality early and often.
http://www-128.ibm.com/developerworks/java/library/j-cq01316/index.html - Jan, 2006
[Top]
