Software Testing Types:
Black box testing – Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.
White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.
Unit testing – Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.
Incremental integration testing – Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.
Integration testing – Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
Functional testing – This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.
System testing – Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.
End-to-end testing – Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
Sanity testing – Testing to determine if a new software version is performing well enough to accept it for a major testing effort. If application is crashing for initial use then system is not stable enough for further testing and build or application is assigned to fix.
Regression testing – Testing the application as a whole for the modification in any module or functionality. Difficult to cover all the system in regression testing so typically automation tools are used for these testing types.
Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer do this testing to determine whether to accept application.
Load testing – Its a performance testing to check system behavior under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test.[1] Software Testing
also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs.
Running software testing projects is far more difficult than people outside of the software testing arena seem to realize. It is not uncommon for senior management, project management and development teams to adversely pressurize the test team to cut corners in order to meet delivery deadlines. Yes, everyone wants to release a quality product, on time and on budget. Believe it or not even the software testing team want to hit the delivery date, with a product that is on budget. Pushing the software testing team to cut corners is not the answer though.
Software Testing is an investigation carried out to provide information about the service or product to the stakeholders. It also provides and independent view to allow people to understand the inherent risks involved in using that software.
Thus it serves as a warning system and prevents possible losses if implemented correctly.
There are various reasons for bugs in software like programming errors, compatibility with earlier / later versions, hardware compatibility, etc. Software testing aims at examining the code and also executing it under test conditions.
Few techniques used for this purpose are:
1) Black box testing,
2) White box testing,
3) Grey box testing,
4) Integration testing,
5) Regression testing,
6) Acceptance testing,
7) Non functional testing and
8) Destructive testing.
As a common practice, an independent testing group does software testing before the product is delivered to the customer. There are many approaches towards software testing. It can be conducted on basic modules or units of the software individually. This is called unit testing. It can also be conducted on the entire software at the same time by putting it through some test cases. This is called system testing. It can be done to check its compatibility with other hardware and software. This is called integration testing. Before the product is dispatched to the client, additional tests called alpha and beta tests are done. Alpha testing includes testing the final version of the product by treating the testers as the end users. Beta testing is done after alpha testing by distributing the product to a select audience outside the testing group for feedback.