SOFTWARE TESTING

  BASICS , TYPES OF SOFTWARE TESTING

INTRODUCTION :

• According to ANSI/IEEE 1059 standard, Testing can be defined as - A process of analyzing a software item to detect the differences between existing and required conditions (that is defects/errors/bugs) and to evaluate the features of the software item.

• In simple words, testing is executing a system in order to identify any gaps, errors, or missing requirements in contrary to the actual requirements. 

WHO DOES TESTING .......? 

• It depends on the process and the associated stakeholders of the project(s).

• In the IT industry, large companies have a team with responsibilities to evaluate the developed software in context of the given requirements. Moreover, developers also conduct testing which is called Unit Testing

•  In most cases, the following professionals are involved in testing a system within their respective capacities:

 Software Tester Software Developer Project Lead/Manager End User

• Different companies have different designations for people who test the software on the basis of their experience and knowledge such as Software Tester, Software Quality Assurance Engineer, QA Analyst, etc.

MYTHS

1. Testing is too expensive.
2. Testing is Time Consuming.
3. Only fully developed products are tested.
4. Complete testing is possible.
5. Missed defects are due to Testers.
6. Testers are responsible for quality of product.
7. Test Automation should be used where ever possible to reduce Time.
8. Anyone can test a software application.
9. A Tester's only task is to find out bugs.

TESTING AND BUGGING

TESTING : Testing involves identifying bug/error/defect in a software without correcting it. Normally professionals with a quality assurance background are involved in bugs identification. Testing is performed in the testing phase.

BUGGING :  Bugging involves identifying, isolating, and fixing the problems/bugs. Developers who code the software conduct debugging upon encountering an error in the code. Debugging is a part of White Box Testing or Unit Testing. Debugging can be performed in the development phase while conducting Unit Testing or in phases while fixing the reported bugs.

TYPES OF TESTING 

There are different types of testing that may be used to test a software during Software development Life Cycle (SDLC).

Manual Testing
Automatic Testing

MANUAL TESTING :

• Manual testing includes testing a software manually, i.e., without using any automated tool or any script.
• In this type, the tester takes over the role of an end-user and tests the software to identify any unexpected behavior or bug. There are different stages for manual testing such as unit testing, integration testing, system testing, and user acceptance testing.

AUTOMATIC TESTING :

• Automation testing, which is also known as Test Automation, is when the tester writes scripts and uses another software to test the product.
• Automation Testing is used to re-run the test scenarios that were performed manually, quickly, and repeatedly.

Software  Testing  Tools

The following tools can be used for automation testing:

                                   -  HP Quick Test Professional

                                   -  Selenium

                                   -  IBM Rational Functional Tester

                                   -  Silk Test

                                   -  Test Complete

                                   -  Testing Anywhere

                                   -  Win Runner

                                   -  Load Runner

                                   - Visual Studio Test Professional

                                   -  WATIR

TESTING METHODS :

There are different methods that can be used for software testing.

Black Box Testing :

•  The technique of testing without having any knowledge of the interior workings of the application is called black-box testing.

•  The tester is oblivious to the system architecture and does not have access to the source code. 

• Typically, while performing a black-box test, a tester will interact with the system's user interface by providing inputs and examining outputs without knowing how and where the inputs are worked upon.

White-Box Testing :

• White-box testing is the detailed investigation of internal logic and structure of the code. White-box testing is also called glass testing or open-box testing. 

• In order to perform white-box testing on an application, a tester needs to know the internal workings of the code.

Grey-Box Testing :

• Grey-box testing is a technique to test the application with having a limited knowledge of the internal workings of an application.

•  In software testing, the phrase the more you know, the better carries a lot of weight while testing an application.

• Mastering the domain of a system always gives the tester an edge over someone with limited domain knowledge.

•  Unlike black-box testing, where the tester only tests the application's user interface; in grey-box testing, the tester has access to design documents and the database. 

• Having this knowledge, a tester can prepare better test data and test scenarios while making a test plan.

                FOR MORE NOTES ABOUT SOFTWARE TESTING ( LEVELS, Alpha Testing, etc...) .............visit the following link www.tutorials.com  by K.K.PANIGRAHI.

THANK YOU FOR READING MY BLOG.......Any queries feel free to post here..

MURALI KRISHNA ATHIPATLA,

MOB : 8520973796,

Email : amkrishna1992@gmail.com.