Basic of Software Testing Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization

What is Testing ? A Process of evaluating a particular product to determine whether the product contain any defects.

Few Testing Examples Specifications for Pen 1.Ink Colour – Red 2.Body Colour – Blue 3.Should be ink Pen

Few Testing Examples Taking Test Ride before buying any vehicle

Few Testing Examples Tasting Recipe for its perfect taste before serving

Software Testing is a process of evaluating a system by manual or automatic means and verify that it satisfies specified requirements or identify differences between expected and actual results. What is Software Testing ?

Why Software Testing ?  To find faults or Defects in Software  To improve Quality of Software  To learn about the reliability of the software  Because failures can be very expensive  To Satisfy Customer in order to stay in Business

What is Defect\Bug ? Error: a human action that produces an incorrect result Fault: a result of an error in software also known as a defect or bug Deviation from requirements Failure: deviation of the software from its expected delivery or service if defect is executed, a fault may cause a failure Failure is an event; fault is a state of the software, caused by an error Failure is an event; fault is a state of the software, caused by an error

Error- Fault-Failure A person makes an error... … that creates a fault in the software... … that can cause a failure in operation

Most Common Software Bugs  Non User Friendly  Incorrect calculation  Incorrect data edits & ineffective data edits  Incorrect matching and merging of data  Data searches that yields incorrect results  Incorrect processing of data relationship  Incorrect coding / implementation of business rules  Inadequate software performance  Unreliable results or performance  Inadequate support of business needs  Incorrect or inadequate interfaces with other systems  Inadequate performance and security controls

Few Reasons for Software Bugs  Miscommunication or no communication  Less understanding of Customer requirements  Software complexity  Programming errors  Changing requirements  Time pressures  Egotistical or overconfident people  Poorly documented code  Not prioritizing test execution.

Damages Caused by Software Bugs  Monetary Loss  Death or Injury  Reputation Loss  Business Loss

What are Testing Myths? Software testing is unnecessary Software test automation can replace test engineers to perform good software testing. Software Testing can be done using Automation tools there is no need of Manual efforts Testing is boring Testers only find bugs Machines will make human testers obsolete Software testing is simple and easy. Anyone can do it. No training is needed. Software Development better domain than Software Testing

What are Testing Principles? Principle #1: Complete testing is impossible. Principle #2: Software testing is not simple. Reasons: Quality testing requires testers to understand a system/product completely Quality testing needs adequate test set, and efficient testing methods A very tight schedule and lack of test tools. Principle #3: Testing is risk-based. Principle #4: Testing must be planned. Principle #5: Testing requires independence. Principle #6: Quality software testing depends on: Good understanding of software products and related domain application Cost-effective testing methodology, coverage, test methods, and tools. Good engineers with creativity, and solid software testing experience

What is Quality ? To satisfy the customers by ensuring that the products or services we provide meet or exceeds the customer requirement& expectations & it should have some value also. Software Testing is directly proportional to Software Quality

Quality Assurance and Quality Control Quality Assurance: A planned and systematic set of activities Necessary to provide adequate confidence that requirements are Properly established and products or services conform to specified requirements. Quality Control: The process by which product quality is compared with applicable standards; and the action taken when non-conformance is detected.

Quality Attributes Reliability Maintainability Usability Portability Correctness Efficiency Integrity or security Testability Flexibility Reusability Interoperability

,