Software testing ppt slides

Successfully reported this slideshow. We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime. Next SlideShares. You are reading a preview. Create your free account to continue reading. Sign Up. Upcoming SlideShare. Embed Size px. Start on. Show related SlideShares at end. WordPress Shortcode. Share Email. Top clipped slide. Download Now Download Download to read offline.

Software testing Jan. Kunal Prajapati Follow. Software engineering lecture notes. This includes, but is not limited to, the process of executing a program or application with the intent of finding software bugs. Testing is a QC activity. Why Does Software Have Bugs? What should the Tester do? Find the bugs 2. Find them early 3. Make sure that they have been fixed What should not the Tester do? Fix the bugs!

Test with good faith! Test with no requirements! Not to report the obvious bugs! Mock at others because of their bugs! Test Planning. Test Analysis and Design. Test Cases preparation.

Test Execution. Test Reporting and Monitoring. Bugs Reporting and Regression Testing. Releasing Reporting. User Acceptance Test Execution. What are the Testing Lifecycle main activities?

Test Planning and Management What are the main components of the good Test Plan? Introduction 1. Resources and Environment Requirements 2. Schedule 4. Test Monitoring and Reporting 5.

How to Verify the Software Requirements What is the Software Requirements Specification Document? The SRS document fully describes what the software will do and how it will be expected to perform.

Complete: The information covers all aspects of this user function. Consistent: The information for this user function is internally consistent. There are no conflicting statements. Correct: The item is free from error. Testable: Can the requirement be easily mapped to specific test cases? Specific :The item is exact and not vague; there is a single interpretation; the meaning of each item is understood; the specification is easy to read.

Use well defined terms and enough information. Relevant: The item is related to the problem and its solution. Understandable: Difficult language should not be used. Be clear. If formal notations are used, make sure they are easy to understand. Figures and tables are helpful, but must be explained. Traceable: The item can be traced to its origin in the problem environment.

Also, you must be able to find who originated a requirement, who wrote it, what other requirement does this one impact. This information is important to make the requirements usable and maintainable changeable.

Am I accessing the right data in terms of the data required to satisfy the requirement. Testing Methods Cont. For example: reviewing, walk through, inspection, etc. Ex: Unit testing, integration testing, system testing. Hence there are various levels of testing.

Testing Levels Cont. Testing Types A test type is focused on a particular test objective 25 Testing Types Cont. Functional Testing: Functional testing refers to activities that verify a specific action or function of the code.

Functional tests tend to answer the question of "can the user do this" or "does this particular feature work. While an application is receiving data from a network, unplug the connecting cable. After some time, plug the cable back in and analyze the application's ability to continue receiving data from the point at which the network connection disappeared. This is generally referred to as software scalability. It is a form of software testing that is used to determine the stability of a given system.

Thank You Nicole Young Nov. Sakshi Bankar Jul. Student at ddit. Show More. Total views. You just clipped your first slide!