Learn Basic Of Software testing

Learn Basic Of Software testing

• 2.
  Software testing isa process of executing a program or application with the intent of finding the software bugs.
• 5.
   Verification isa process of evaluating the intermediary work products of a software development lifecycle to check if we are in the right track of creating the final product. Basically verification refers to the internal structure of the product (architecture & coding level)  Validation is the process of evaluating the final product to check whether the software meets the business needs. Basically validation refers to the behavior and expected outcome of the product (interface and external level)
• 6.
  Inspection Software Testing Static TestingDynamicTesting White Box Informal Reviews Walk-Through Black Box Technical Reviews
• 7.
  Static testing cantest and find defects without executing code. Static Testing is done during verification process. This testing includes reviewing of the documents (including source code) and static analysis. This is useful and cost effective way of testing.
• 8.
  Static testing involvesa series of procedures and technique that evaluate the software for possible errors and bugs.  Informal Reviews-A review not based on a formal (documented) procedure.  Walkthroughs-A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content.
• 9.
   Peer Reviews-A review of a software work product by colleagues of the producer of the product for the purpose of identifying defects and improvements.  Technical Reviews- A review characterized by documented procedures and requirement.  Inspection- A type of peer review that relies on visual examination of documents to detect defects, eg., violation of development standards and non- conformance to higherlevel documentation. - To carry out testing as early as possible - Finding and fixing defect more cheaply
• 10.
  Dynamic Testing isa kind of software testing technique, using which the dynamic behavior of the code is analyzed.
• 11.
  White Box Testingis a software testing method in which the internal structure/ design is known to the tester. The main aim of White Box testing is to check on how System is performing based on the code.
• 13.
  Black Box Testingis a method of testing in which the internal structure/ code/design is NOT known to the tester. The main aim of this testing to verify the functionality of the system under test and this type of testing requires to execute the complete test suite and is mainly performed by the Testers, and there is no need of any programming knowledge.
• 16.
  Different Phases fortest design and implementation  Features to be tested  Derive the Test Conditions  Derive the coverage Items  Derive the Test Cases We have to ensure that Testing Environment should always be similar to the Production environment, in this phase we have to install the build and manage the test machines.
• 17.
  During this phase,test cases are actually executed. Based on the Execution if the Expected and Actual Results are not same then the Test case has to be marked as Fail and a Bug should be logged.