Used price: $8.00
Buy one from zShops for: $12.77
Used price: $1.11
Collectible price: $4.24
Buy one from zShops for: $2.53
Main characters: There were 6 hedgehogs: 1. Rosie was a mother of four whose leg was run over by a car. 2. Scout explored, and wandered, and was eaten by a badger. 3. Spike was the heaviest guy. Spike was named for his tail. It always went up like a spike. 4. Tiggy named for her clumsiness and size. 5. Speedy named for his incredible speed. He was the loudest of the lot. He helped Guy. 6. Guy was first found in a net farmer used for potting beans and plants. He was blind and was helped by Speedy. There were 3 children: 1. Mandy, a girl adopted by vets, has an interest in animals. She wanted to help the animals. She got all her knowledge from her parents. 2. James was Mandy's best friend. James' father, Mr. Hunter, was the very first to find Rosie and her babies and he almost put a pitchfork through her. 3. Claire found Guy, a blind hedgehog. Her father, a doctor, ran over Rosie's leg with his silver car. He turned his front yard into a hedgehogs' hotel.
Summary of the book: Rosie, a mother of four, was run over by a car. Her babies had to be nursed as well because if they were abandoned, they could be eaten by badgers and foxes. Then Guy was found. He was helped by Speedy, who followed him around, helping him, being his eyes, because Guy was blind. They were nursed by Mandy Hope, James Hunter and Claire McKay. There were four baby hedgehogs, but only three survived because Scout was eaten by a badger.
My personal reaction to the book: I think this book is sad, enjoyable and very well-written. It makes you really want to read on and on until you finish. But when you finish, you have this empty, hollow feeling. You got the hollow feeling because you've enjoyed the book so much. You really want to read on and on forever, but it always have an end. When it does end, you want more to read. I always like hedgehogs. I really like the hedgehogs in this story. I wish it wasn't so sad. It would be good if Scout wasn't killed. He was just wounded and he had to be nursed.
Used price: $2.43
Collectible price: $7.50
Buy one from zShops for: $7.99
Used price: $0.21
Buy one from zShops for: $2.47
By: Ben M Baglio
This heartwarming story is about Alex Hastings who is sick in Europe. For a Christmas gift Alex and her family are going to America for the operation. Three days before Christmas, Amber, the cat, is missing. Can they find her, or will she freeze?
I like this book because it has excitement. It takes you and draws you in. It's sad when Amber is missing. I like Mandy in this book because she will do anything to save an animal in need.
I think the main idea in this book is that friendship never ends. Alex doesn't want to leave Amber in Europe. See if Alex will solve her problem! Ben Baglio makes you think about your cat or pet and makes you wonder if your pet would run away in the freezing cold.
Used price: $6.22
Buy one from zShops for: $6.05
This is all i need to say
My only gripe is the exclusion of Dr. Samuel Johnson from the list. The man wrote the first English Dictionary - what's more influental that that? But the fact that you can argue with Burt's lineup while at the same time seeing the sense of his choices - that's what makes for an excellent piece of work.
Used price: $100.00
Collectible price: $50.00
Buy one from zShops for: $15.95
The novel moves quickly and flows nicely. The characters are strong. You find yourself somehow inside Corporal Courcey's head and laughing at Captain Olivetti's obsession with his CIB, his combat infantry badge. The role of Major Barker in the book is much less central than it is in the movie. But then, Burt Lancaster played the ... out of Major Barker in the film, so they may have made certain adjustments for the star.
There is a sadness and fatalism about the book that may bother some. However, the topic is not exactly uplifting. On the whole, a worthwhile and enjoyable read.
Used price: $35.00
Buy one from zShops for: $37.36
Too many times have automated test tools become shelfware, or the cost of maintaining the scripts prohibitvely expensive. The authors of this book offer a simple and easy to use data-driven framework that can minimise scripts and human effort. They place their framework within the Rational Unified Process (RUP).
The book offers actual and detailed advice that goes all the way down to code and script templates. Based mostly on Rational tools, the book gives lip service to Winrunner and anything said can be translated to any automated tool.
Their open-source framework is the Control Synchronized Data Driven Testing(CSDDT). Data to be input, keywords to navigate through the application and actions to be performed are held in the spreadsheet. There are four main scripts: A Main script that reads and processes the records; a window selection script, a tab selection script, an action script and error handling script. Data input is held in an array and there is a comment field that documents the test record. Your application code is held in a switch statement, and it is highly conceivable that your project can have single figure script numbers. There is also a script that converts the spreadsheet data in a .csv file that is read by the Main script. There is detailed
information given on how to implement the CSDDT. It is a framework I use and am pleased with.
There are two interesting chapters on Unit and Integration testing. Like eXtreme Programmers they believe in automating unit tests that pass at 100% before submitting for build. They correctly argue that unit tests should be constructed before development code is written and they also point to the xUnit group of tools.
They make insightful points about the necessity of integration testing: Could you not help but identify with the following statements: "... We have seen two chronic problems: First, the build fequently does not install on system test machines. Second, the fact that unit and integration testing has not been done previously forces the system test team to do tests that development should have already executed." Again they also argue for automated integration testing else "it will not get done."
I feel however that Mosley and Posey's ideas need to be infused with agile values and practices. For example do we really need improved software requirements documentation, verbose Test Plans and meticulous test design when requirements change so much? Do we really need all these Rational tools and the time it takes to use and update them? Can we not make automated functional tests an integral part of requirements? What about Pair Test Programming? How are we going to increase oral communication? Is devolopment and test a false dichotomy? These kind of issues also need to be addressed as we begin to construct software in a radically different way.
While the book is well written and easy to read for someone who's familiar with software testing and who may have some experience with test automation, it assumes that the reader does have experience in the field.
The authors begin by reviewing important fundamental practices of software testing that are critical to effectively sustaining both manual and automated testing efforts. They provide recommendations on how to approach test automation for each phase of the software development lifecycle beginning with requirements through the final stages of testing. The authors present very specific recommended techniques and tools and offer many examples using a data driven framework with emphasis on Control Synchronized Data Driven Testing (CSDDT). Most often the tools mentioned and examples provided are those offered by Rational, Inc. as well as the use of Microsoft Excel. Frequently, automated tools from other vendors are referenced when they are applicable to the technique being discussed. They provide references to books and to several web links that offer sources of information on similar frameworks using other tools. The authors include useful information in the appendices such as a captured discussion on the subject of the data driven approach by leading practitioners, automated testing definitions, an example test automation project plan, and a test automation project work plan template.
Some of the key points in the book include the importance of identifying and documenting application and testing requirements as well as documenting test cases and conditions. They emphasize the importance of planning for test automation and implementing it similar to any other software development effort. This includes the separation of roles between test designer and test implementer. They urge that test automation be performed at most phases of software development including unit testing, but that it primarily be used for regression testing. The key success factor for test automation is the maintainability of test scripts. The authors point out that this is extremely difficult using a capture/playback method of implementation and that a data driven approach using modular scripts has shown to be much more successful in the long run. The authors do a good job of describing these key points and then making specific recommendations with examples on how to implement them.
As a practitioner of test automation, and reviewer of this book, I very much agree with these key recommendations and support the authors' intent to educate people implementing test automation as these key points can be the difference between failure and success.