Sunny Day Testing

Sunny Day Testing is a collection made with a variety of a hot palette of colors, with a black outline on the right side of each icon that gives a wonderful weight and volume of the graphic, they inclination plays a nice role, making the graphics completely flexible to use. Cool icons with a cartoonish design. Different from any others stocks, Sunny Day has been illustrated with a 3D concept. Our new stock was designed inspirited in children  and their toys, but is perfectly suitable to give a special shine concept with the stroke in neutral tonalities of any software and web applications.

This diverse stock contains all the aspects related to projects management. You can find here all the steps to keep a project flowing. The beginning of a well-planned project where the analysis to concrete if a project is feasible and productive is the most crucial aspect; you can find a graphic to represent a signed contract, custom relations, organization, and also a chart with responsibilities assigned. Following the most crucial steps to keeps a successful project going in the right track you can also find human resources, data management, supplies and testing. These icons are a great way to enhance your applications as well as motivators for all the people involved in the development of the project such as employees, staff and clients.

Design Driven Testing (Sunny/Rainy Day)

Whilst reading through Design Driven Testing (ISBN 978-1-4302, I came across a very telling statement concerning the expansion of use cases. This was in the context of sunny days (default course through the application) and rainy days (the paths travelled when things go wrong).

The quote I want to share with you is this: "If the rainy days scenarios are not explored in sufficient depth before coding begins, all sorts of nasty surprises can leap up during coding, often resulting in a need to rethink the design."

The authors are correct that often we are rushed into design, without properly considering all required outcomes in a given scenario.

The only shortcoming, so far I can find about this book is that the examples are from the world of UML and J*** and not Visual Studio/C#.  Otherwise, I would recommend it all my fellow web developers. Certainly all those responsible for Technical Design of applications should read this book as it contains much useful insight into good practical design that requires only refinement not continual rewriting.