Applications Books

Finally we may play with the "building blocks of matter" we've been hearing so much about. Here is an instruction manual, detailing the Elements, and their Interactions, while at the same time suggesting possible Design Models for construcion.

Curious about the subject?
Start with Drexler's Engines of Creation, instead. Maybe some other collections of theoretical applications to whet your appetite. Come back to this when you begin to see a bigger picture.

Know some, want to know more?
Definately read. But be warned, it is quite techincal when it is not being necessarily vague. This is a halmark. The basis of this book was Drexler's thesis for his doctorate in Molecular Nanotechnology, the first awarded (MIT 1991, I believe).

Serious about the topic?
You already have access to a copy...or should.

You might very well be able to download significant portions from Foresight's website (it's an org.anization, not a com.mercial); but I would suggest supporting them with at least the price of the book. They seem to be committed to developing this Potential responsibly.

Your book is an excellent guide. Thank you for inviting me to the field of nanotechnology.

Sincerely,

Kenneth L. Buckingham, Founder Tiny Technology, Inc.

I agree with the book that the .NET Framework is mostly targeted at business developers and the Internet for B2B and B2C applications, as well as internal Enterprise applications. Having said that, I have found the .NET framework lacking, and as the author points out, most likely due to how young it is in comparison to the Win32 API.

This book will get you up and running with making those Win32 API calls when you can't find that same functionality duplicated in the .NET Framework. There isn't much documentation on this subject matter on MSDN or the web (searching on Google), so this is pretty much it. The author did a great job, however, at times, the examples were a little light or topics weren't explained as thoroughly as they should have been. For example, the author will tell you what data type he used in place of a native Win32 data type, but doesn't clearly explain his reasoning for the choice. But other than that small complaint, this book is a must have for any .NET developer.

Although process mostly keeps the same even with R/3 upgrading, there would still have some big changes between version 3.0 which this book refers to and the version 4.X. And I really hope this book could have second edition and explore more on the MTO process instead of only 30 pages in the last chapter.

This is really the best SAP book I've read!

BTW: The book has more than 840 pages, not 448 as mentioned in the book information!

Michael Czeiszperger
Web Performance, Inc. Stress Testing Software
http://www.webperformanceinc.com

That said, instead of this book you should get the second edition, which is a major rewrite, and also expanded in scope to include testing mobile systems. This edition is titled, "Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems" ISBN 0471201006, and is everything others have said about this first edition - and more!

Even with a better second edition, this book deserves the five stars I gave it because of the influence it has had on the testing profession. Moreoever, this first edition is not out-of-date, and is still a great book if you don't need information about testing mobile web systems at this time (although it's a safe bet you will in the future).

The shade of grey can vary from white box testing (full review of source code) to black box testing (no review of source code). You choose what level of information to gather depending on your budget, capabilities and judgment.

This book provides the first detailed approach to grey box testing, focussing on web-based application architectures. These architectures are based on a heavy use of components: application servers, web servers, load balancers, databases and the like. This book describes these components, suggests how they can fail and what you can do to anticipate, trigger, or detect such failures.

This approach is supported by the author's extensive experience testing web-based (and other) applications as president of a software testing company. It is augmented by plenty of good advice on how to communicate test results clearly.

Hung Nguyen and I are co-authors of another book and good friends. I am not an unbiased reviewer. On the other hand, I wouldn't write this review if I didn't believe every word of it.

Hung's book breaks new ground. It will be useful today, and I believe it will have lasting value and influence.

Once you get beyond the superficial (not unimportant, but much less difficult) issues of usability testing that dominate so many discussions of web testing, you run into the really tough problems of web application testing. Hung Nguyen's book is about those harder problems.

The web-based application runs on a wider range of platforms than any other type of program in history. It doesn't even have control over its presentation layer (the user supplies the browser and the multimedia plugins, and these applications might change any time). What will the application look like on the changed browser? The application probably also relies on third party databases (which can change any time), third party network connections (which can change any time), third party security systems and other access control (which can change any time), etc., etc. Almost anything in this system can change any time. How do you deal with a system that has so many unknowns?

Hung's view is that web application testers must learn more about the technical details of the systems and understand how external variables can interact (and fail) with the application under test.

To help testers learn about the interaction (and testing) of applications with other system components, he wrote the field's first book on grey box testing.

This book has substantial value for what it teaches us about testing on the web. Beyond that, it teaches about thinking clearly and thoroughly when your application interacts in complex ways with other systems. I think his approach will have lasting value and lasting influence long after many of the detailed issues that he describes have been resolved and replaced with new ones.

Along with the original approach, Hung gives a powerful real-world example. He is the president of a company that publishes a web-based bug tracking system. To illustrate the types of tests that you can run and the types of bugs you can find, he opened his records and described real tests, real bugs, and real testing problems. It's a rare treat to see a discussion of testing experience by someone who knows testing, who also intimately knows the software under test, and who isn't constrained in what he can say by a nondisclosure contract.