Overview of Software Testing

Slide 1:

Prepared By: Sudipta Naha

Slide 2:

What is Testing Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test Software testing can also be stated as the process of validating and verifying that a software program/application/product: Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs (errors or other defects). meets the business and technical requirements that guided its design and development; 2. works as expected; and 3 . can be implemented with the same characteristics Objective

Slide 3:

Importance of Testing in Software Industry In the whole development process, testing consumes highest amount of time. But most of the developers oversee that and testing phase is generally neglected. As a consequence, erroneous software is released. The testing team should be involved right from the requirements stage itself Every software product has a target audience. For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers, and other stakeholders. Software testing is the process of attempting to make this assessment.

Slide 4:

A sample testing cycle

Slide 5:

Different Type of testing There are different testing techniques/procedures/terms used which can be further categorized as below :

Slide 6:

Functional Testing Profile The different phase of a functional testing under a project can be categorized as below: The different procedure of testing followed by a functional tester is as below: The different objective of a functional Tester is as below: Unit Testing or White Box Testing System Testing System Integration Testing or SIT or Black Box Testing or End to End Testing User Acceptance Testing or UAT Production Testing Manual Testing Automation Testing Regression Testing or Smoke Testing or Sanity Testing New Functionality Testing Acceptance Testing

Slide 7:

Automation Testing Notable test automation tools Tool name Produced by Latest version HP QuickTest Professional HP 11.0 IBM Rational Functional Tester IBM Rational 8.1.0.3 Parasoft SOAtest Parasoft 9.0 Ranorex Ranorex GmbH 3.0 Rational robot IBM Rational 2003 Selenium Open source 1.0.10 SilkTest Micro Focus 2010 TestComplete SmartBear Software 8.2 TestPartner Micro Focus 6.3 TOSCA Testsuite TRICENTIS Technology & Consulting 7.2.1 Visual Studio Test Professional Microsoft 2010 WATIR Open source 1.6.5 WebUI Test Studio Telerik, Inc. 2010.3 Test automation is the use of software to control the execution of tests , the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions during functional testing. Commonly, test automation involves automating a manual process already in place that uses a formalized testing process.

Slide 8:

An Overview of non-functional Testing- Performance and Load Testing Performance testing is executed to determine how fast a system or sub-system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage Load testing is primarily concerned with testing that can continue to operate under a specific load, whether that be large quantities of data or a large number of users. This is generally referred to as software scalability. The related load testing activity of when performed as a non-functional activity is often referred to as endurance testing . :NOTE: There is little agreement on what the specific goals of load testing are. The terms load testing, performance testing, reliability testing, and volume testing, are often used interchangeably. TOOLS In the diagnostic case, software engineers use tools such as profilers to measure what parts of a device or software contributes most to the poor performance or to establish throughput levels (and thresholds) for maintained acceptable response time.

Slide 9:

Testing Tools and Techniques

Slide 10:

A Briefing

Slide 11:

Questions ??? Or Suggestions

Slide 12:

Thank you for your patience 