What are the Different types of Testing in software engineering? How to design a Test Case?
What is Testing in Software Engineering
Testing is running the program(or product) under various circumstances and conditions to find errors and bugs in it. This is important as releasing a faulty product will not only cause serious problems to the end user, it will also harm the companies reputation. There are various kind of Testing conditions and which one to use depends on type of product.
Types of Testing in Software Engineering
As per Test Target, there is * Unit Testing * Integration Testing * System Testing As per Test Objective, there is * User Acceptance Testing * Installation Testing * Functional * Alpha / Beta testing * Regression * Performance * Stress * Usability * Configuration * Smoke (Sanity Test) Let's see them one by one -
Unit Testing
- The Tools used in Unit Testing are debuggers, tracers and is Done by Programmers. Unit testing verifies the functioning in isolation of software pieces which are separately testable.
Integration Testing
- According to IEEE, Integration Testing is An orderly progression of testing in which software elements, hardware elements, or both are combined and tested, to evaluate their interactions, until the entire system has been integrated. It Test against system design and Focuses on communication between modules start with one module, then add incrementally. Various Types of Integration Testing are: * big bang approach - Integrate
Everything at once * top-down approach - Keep on breaking the system in parts one by one and than test each part. * bottom-up approach - Test the small parts first and than keep on integrating the system and keep on testing the bigger module of it. * mixed approach - Done by help of stubs (Dummy modules)
Sysem Testing
- IEEE Defines it as The process of testing an integrated hardware and software system to verify that the system meets its specified requirements. It is tested against system specification. May test manual procedures, restart and recovery, user interface, stress, performance. In System Testing, real data is used and sometimes users participations is also used.
Objective Based Testing
Some of the testing under this category and what they mean are as follows - *
User Acceptance Testing
- Testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. It is Done against requirements and is done by actual users. *
Installation Testing
- System testing conducted once again according to hardware configuration requirements. Installation procedures may also be verified *
Functional Testing
- It checks that the functional specifications are correctly implemented. Can also check if Non Funcctional behavior is as per expectations. *
Stress testing (aka endurance testing)
- We impose abnormal input to stress the capabilities of the software. Input data volume, input data rate, processing time, utilization of memory, etc. are tested beyond the designed capacity. *
Regression Testing
- Regression Testing accdoing to IEEE is "selective retesting of a system or component to verify that modifications have not caused unintended effects". It is repetition of tests intended to show that the software’s behavior is unchanged, except insofar as required. It Can be done at each test level. *
Performance Testing
- It is verifying that the software meets the specified performance requirements (response time, volume ..)
Alpha / Beta testing
- Probably one term which you must be aware of as we often hears this software is in Alpha phase and in Beta phase. Here Testing is done by representative set of potential users for trial use. Please Note - in-house (alpha testing) - external (beta testing)
Usability Testing
- It evaluate the Human Computer Interface. Verifies for ease of use by end-users. Verifies ease of learning the software, including user documentation. Checks how effectively the software functions in supporting user tasks. Checks the ability to recover from user errors.
Configuration Testing
- It is Used when software meant for different types of users. It also check that whether the software performs for all users.
Smoke (Sanity Test)
- It is used to Verify whether the build is ready for feature/requirement based testing).
Recovery Testing
- It is used in verifying software restart capabilities after a disaster•
Security Testing
- It is ued toverify proper controls have been designed.
How to Design a Test Case
This Question is often asked in microsoft of from any other company who is looking to hire you for testing work. A test case will have 5 section -
Testing is running the program(or product) under various circumstances and conditions to find errors and bugs in it. This is important as releasing a faulty product will not only cause serious problems to the end user, it will also harm the companies reputation. There are various kind of Testing conditions and which one to use depends on type of product.
Types of Testing in Software Engineering
As per Test Target, there is * Unit Testing * Integration Testing * System Testing As per Test Objective, there is * User Acceptance Testing * Installation Testing * Functional * Alpha / Beta testing * Regression * Performance * Stress * Usability * Configuration * Smoke (Sanity Test) Let's see them one by one -
Unit Testing
- The Tools used in Unit Testing are debuggers, tracers and is Done by Programmers. Unit testing verifies the functioning in isolation of software pieces which are separately testable.
Integration Testing
- According to IEEE, Integration Testing is An orderly progression of testing in which software elements, hardware elements, or both are combined and tested, to evaluate their interactions, until the entire system has been integrated. It Test against system design and Focuses on communication between modules start with one module, then add incrementally. Various Types of Integration Testing are: * big bang approach - Integrate
Everything at once * top-down approach - Keep on breaking the system in parts one by one and than test each part. * bottom-up approach - Test the small parts first and than keep on integrating the system and keep on testing the bigger module of it. * mixed approach - Done by help of stubs (Dummy modules)
Sysem Testing
- IEEE Defines it as The process of testing an integrated hardware and software system to verify that the system meets its specified requirements. It is tested against system specification. May test manual procedures, restart and recovery, user interface, stress, performance. In System Testing, real data is used and sometimes users participations is also used.
Objective Based Testing
Some of the testing under this category and what they mean are as follows - *
User Acceptance Testing
- Testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. It is Done against requirements and is done by actual users. *
Installation Testing
- System testing conducted once again according to hardware configuration requirements. Installation procedures may also be verified *
Functional Testing
- It checks that the functional specifications are correctly implemented. Can also check if Non Funcctional behavior is as per expectations. *
Stress testing (aka endurance testing)
- We impose abnormal input to stress the capabilities of the software. Input data volume, input data rate, processing time, utilization of memory, etc. are tested beyond the designed capacity. *
Regression Testing
- Regression Testing accdoing to IEEE is "selective retesting of a system or component to verify that modifications have not caused unintended effects". It is repetition of tests intended to show that the software’s behavior is unchanged, except insofar as required. It Can be done at each test level. *
Performance Testing
- It is verifying that the software meets the specified performance requirements (response time, volume ..)
Alpha / Beta testing
- Probably one term which you must be aware of as we often hears this software is in Alpha phase and in Beta phase. Here Testing is done by representative set of potential users for trial use. Please Note - in-house (alpha testing) - external (beta testing)
Usability Testing
- It evaluate the Human Computer Interface. Verifies for ease of use by end-users. Verifies ease of learning the software, including user documentation. Checks how effectively the software functions in supporting user tasks. Checks the ability to recover from user errors.
Configuration Testing
- It is Used when software meant for different types of users. It also check that whether the software performs for all users.
Smoke (Sanity Test)
- It is used to Verify whether the build is ready for feature/requirement based testing).
Recovery Testing
- It is used in verifying software restart capabilities after a disaster•
Security Testing
- It is ued toverify proper controls have been designed.
How to Design a Test Case
This Question is often asked in microsoft of from any other company who is looking to hire you for testing work. A test case will have 5 section -
What is SRS?
SRS stands for Software Requirement Specification.
It establishes the basis for agreement between customers and contractors or suppliers on what the software product is expected to do, as well as what it is not expected to do.
Some of the features of SRS are -
It establishes the basis for agreement between customers and contractors or suppliers on what the software product is expected to do, as well as what it is not expected to do.
Some of the features of SRS are -
It sets permits a rigorous assessment of requirements before design can begin.
It sets the basis for software design, test, deployment, training etc. It also sets pre-requisite for a good design though it is not enough.
It sets basis for software enhancement and maintenance.
It sets Basis for Project plans like Scheduling and Estimation.
What are Functional and Non Functional Requirements in Software Engineering?
Functional Requirements are the Expected functionality or services from the system.
Non - Functional Requirements are System property and constraints. Now Constraints can be on requirements itself. Some examples are of Response time, 24X7 availability of the system etc.
<Back
Non - Functional Requirements are System property and constraints. Now Constraints can be on requirements itself. Some examples are of Response time, 24X7 availability of the system etc.
<Back
For more SE Interview Questions and answers DOWNLOAD PDF from here.
24 Aug 2013
0 comments:
Post a Comment