Software Testing: A verification method that applies a controlled set of conditions and stimuli for the purpose of finding errors. This is the most desirable method of verifying the functional and performance requirements. Test results are documented proof that requirements were met and can be repeated. The resulting data can be reviewed by all concerned for confirmation of capabilities.
Bug / Defect / Error:
Software is said to have Bug if it features deviates from specifications.
Software is said to have Defect if it has unwanted side effects.
Software is said to have Error if it gives incorrect output.
Test Case: A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results.
Test Plan: A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it.
Subscribe to:
Post Comments (Atom)
2 comments:
Hi Pranjul,
Last week I have faced one interview. The interviewer asks me about Prioritizing Testing.
Pl. tell me the exact ans.
When less time is available for testing, in that case we perform the Prioritizing Testing. A team of members seat together and identify the functionalities for Prioritizing Testing.
Post a Comment