• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Significance Of Unit Testing
 

Significance Of Unit Testing

on

  • 2,673 views

It doesnt cover the entire topic in details...just few major issues and points which we discovered during our Test Life Cycle

It doesnt cover the entire topic in details...just few major issues and points which we discovered during our Test Life Cycle

Statistics

Views

Total Views
2,673
Views on SlideShare
2,672
Embed Views
1

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Significance Of Unit Testing Significance Of Unit Testing Presentation Transcript

    • SIGNIFICANCE OF UNIT TESTING
    • What is Unit Testing?
      Unit testing is a software development process in which the smallest testable parts of an application, called units, are individually and independently scrutinized for proper operation. Unit testing is often automated but it can also be done manually.
      This testing mode is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.
      Unit testing involves only those characteristics that are vital to the performance of the unit under test. This encourages developers to modify the source code without immediate concerns about how such changes might affect the functioning of other units or the program as a whole
    • Advantages of Unit Test
      Problems are found early in the development cycle.
      Code that works now, will work in the future.
      New features will not break existing functionality.
      Making change becomes easier, as controls are in place.
      The development process becomes more flexible.
      Implementation design is improved as APIs are forced to be more flexible and unit-testable.
      Bringing new developers on board becomes easier and improves teamwork. Unit tests document the code.
      The need for manual testing is reduced.
      The development process becomes more predictable and repeatable.
    • What should be tested when Unit Testing?
      For a UI screen include test cases to verify all the screen elements that need to appear on the screens
      For a UI screen include Test cases to verify the spelling/font/size of all the “labels” or text that appears on the screen
      Create Test Cases such that every line of code in the unit is tested at least once in a test cycle
      Create Test Cases such that every condition in case of “conditional statements” is tested once
      Create Test Cases to test the minimum/maximum range of data that can be entered. For example what is the maximum “amount” that can be entered or the max length of string that can be entered or passed in as a parameter
      Create Test Cases to verify how various errors are handled
      Create Test Cases to verify if all the validations are being performed
    • Most Frequently Found Issues
      Spelling mistakes
      Misinterpretation of requirements
      Validations not handled like empty string, DbNull checks, time zone issues etc
      Connection string passed is incorrect
      Data Source name used is not uniform
      Validation and Warning messages not generic enough
      Improper Error handling
      Dependent codes not analyzed clearly[CR of one conflicting with functionality of other]
      Design Issues
      Customization changes not conveyed
      Values are hardcoded for configurable items(like messages, datasourcename)
      Filtered views were not getting used at all places
      Continuous changes in requirement were not kept track off
    • THANKYOU