Successful software depends as much on scrupulous testing as it does on solid architecture or elegant code. But testing is not a routine process, it's a constant exploration of methods and an evolution of good ideas.
Beautiful Testing offers 23 essays from 27 leading testers and developers that illustrate the qualities and techniques that make testing an art. Through personal anecdotes, you'll learn how each of these professionals developed beautiful ways of testing a wide range of products -- valuable knowledge that you can apply to your own projects.
Here's a sample of what you'll find inside:
All author royalties will be donated to the Nothing But Nets campaign to save lives by preventing malaria, a disease that kills millions of children in Africa each year.
This book includes contributions from:
5 Key Tips and Tricks for Testingby Tim Riley
1. If you are going to run a test more than 3 times, think hard about automating it. The time saved is more than worth the front-end investment.
2. Test the riskiest, most changed, and most complex areas first, since they are most critical. These may be tests #10, #35 and #99. But if you start at test #1 and methodically work you way towards test #100 you may never get to #35 and most likely not #99.
3. Always take time to think through the testing before jumping in. This is the "Ready"part of Ready, Aim, Fire. Many testers jump straight to "Fire" and don't know what they are shooting at. This includes talking to the developer, talking through the testing with others, and writing down a plan and asking for feedback. This provides a way to see if you achieved what you originally planned and gives you something to build on in the future.
4. Have the tests ready _before_ the feature is done, or at least very soon after. Testing a week after a feature is done is a hundred times better then testing it a month later. And a thousand time better then testing is 6 months later.
5. Get to know your developers. Not just to show them your test plan and send them bug reports. Go to lunch with them. Walk to meetings with them. Make sure you know what they are working on and what their plans are. And make sure they know what you are working on and what your plans are. By having a richer working relationship, they will remember to include you when new features come alone, requirements change, and plans are updated. And they will eagerly help you out when developing test cases!
Die Inhaltsangabe kann sich auf eine andere Ausgabe dieses Titels beziehen.
Tim Riley is the Director of Quality Assurance at Mozilla. He has tested software for 18 years including everything from spacecraft simulators, ground control systems, high security operating systems, language platforms, application servers, hosted services and open source web applications. He has managed software testing teams in startups to large corporations consisting of 3 to 120 people in size and in up to 6 countries. He has a software patent for a testing execution framework which matches test suites to available test systems. He enjoys being a breeder caretaker for Canine Companions for Independence (cci.org) along with live and studio sound engineering.
Adam Goucher has been testing software professionally for over ten years. In that time he has worked with start-ups, large multi-nationals and ones in between in both traditional and agile testing environments. A believer in the communication of ideas big and small, he writes frequently at http://adam.goucher.ca and teaches testing skills at a Toronto area technical college. In his off hours he can be found either playing or coaching box lacrosse - and then promptly applying lessons learned to testing. He is also an active member of the Association for Software Testing.
„Über diesen Titel“ kann sich auf eine andere Ausgabe dieses Titels beziehen.