Software testing
From Wikiversity
 Please help develop this page
This page was created, but so far, little content has been added. Everyone is invited to help expand and create educational content for Wikiversity. If you need help learning how to add content, see the editing tutorial and the MediaWiki syntax reference. To help you get started with content, we have automatically added references below to other Wikimedia Foundation projects. This will help you find materials such as information, media and quotations on which to base the development of "Software testing" as an educational resource. However, please do not simply copy-and-paste large chunks from other projects. You can also use the links in the blue box to help you classify this page by subject, educational level and resource type. |
|
Software Testing Concepts The name itself explains itself nicely.Imagine writing a school paper what if you yourself had prepared the question paper , you had yourself answered it and above all you had yourself corrected the paper.I bet you would have given yourself full marks. Testing of a particular product is especially encouraged to be done by an independent body/person who is not directly associated with the development of product itself, This gives the tester an unbiased view for testing the product thoroughly. Although i am writing these notes just for software testing the same principle applies to product testing for any industry be it software or anything else right from pencils to airplanes.
Why Testing is important ? Testing plays a very important role in knowing how well the product has been built to match the required specifications. Just think on these two lines " Have you built the product right"
"Have you built the product Rightly"
Thinking over these two statements will give you the feeling that these are two questions that need to be answered if you want to ensure the Quality of the product (software in this case) One question emphasizes on building the right product while the other emphasizes on laying down stringent processes so that you build the product right.
One question refers to building a product to meet the specific requirements , while other shows the road to build that product in a right manner. That is how the concept of Quality Assurance and Quality Control has come into picture. One builds a strong frame work of processes to build the right product while Control thoroughly checks it/validates it to ensure it's working properly as per it's functionality.
Timely testing is very important concept.Why I stress on Timely is because a stitch in time saves nine :) The more earlier you find a bug you can more rapidly fix it and the eventually lesser components of the product are affected. Imagine building a mega storey building and realize that you do not test it enough and once you reach the construction of the 10 the floor you realize there is a problem with the 1 st floor .you will have to find a hiding place for yourself very soon if you land up in such situation. Try and map this with the process of software product development and you will realize the importance of timely identification and resolution of a bug.
Levels of testing:
