To celebrate the publication of six new Microsoft books on Monday, 24th January 2011 Packt has a special offer on all the latest Microsoft books
Purchase 2 or more Microsoft books and get 25% off each book throughout January
Read Test Microsoft Monday Campaign in full
WordPress is a flexible and powerful tool that's ideal for creating both blog and non-blog websites. You can customize the features, incorporate your own design, and even write your own plugins with ease. Its versatility and ease of use have attracted a large, enthusiastic, and helpful community of users.
To celebrate the publication of the WordPress 3.0 Complete book, Packt is offering a series of attractive discounts on all WordPress books for a period of 10 days.
* Buy any WordPress print book and get 20% off
* Buy any WordPress eBook and get 30% off
This offer will last for a 10 day period starting from 18th February and ending 28th February 2011. Grab your copy now !
Read Test Page in full
In this article by Evgeniy Sharapov, author of the book Instant Apache Camel Messaging System, we will learn about testing a Camel application. Of course, it is very easy to start your application and see how it works while it is small. Once the application starts growing, it will become impossible to check that it works correctly. Furthermore, Camel is both concurrent, which makes it even more complex, and an integration framework, so one would expect inputs and outputs to come and go from and to other systems, which might make things very tedious for the person doing quality assurance. Well, a long time ago, software developers came up with an idea to automate testing. Since then, plenty of good frameworks and libraries facilitating automatic testing have emerged. One of the approaches is unit testing—testing an application's functionality piece by piece or unit by unit. In the Java world, there are two options for unit testing: JUnit and TestNG. Even though Apache Camel supports both, here we will use only JUnit.Read Testing a Camel application in full
It is always necessary to have a Help section in our software application. When users do not find a way out from a specific problem in our application, it is the help section they turn to. Hence it is important that the help feature is well maintained and without any errors. In this article by Tim Lavers and Lindsay Peters, we will see the errors that can occur in our help section and how to test the help section.Read Testing a HELP System in a Java Application in full
In this article by Tim Lavers and Lindsay Peters, we will be studying in detail the test for an extremely simple user interface component. It will involve UI Wrappers for components as a way of safely and easily manipulating them in tests and specific techniques for reading the state of our user interfaces. Although the component that we'll be testing in this article is simple, it will still allow us to introduce a few specific techniques for testing Swing user interfaces. It will also provide us with an excellent opportunity for showing the basic infrastructure that needs to be built into these kinds of tests.Read Testing a Save As Dialog in Java using Swing in full
Some of the things that we will cover in this two-part article by Carlos de la Guardia, author of Grok 1.0 Web Development, includes:
- Need for testing
- Testing in Grok
- Extending the functional test suite provided by grokproject
- Other kinds of testing
- Debugging tools
- Testing a WF program with unit test framework
- Debugging a WF program