What Kinds Of Software Testing Should Be Considered

What Kinds Of Software Testing Should Be Considered

Black box testing - This form of Testing is just not based mostly on any data of inner design or coding. These Tests are primarily based on requirements and functionality.

White box testing - This relies on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.

Unit testing - essentially the most 'micro' scale of testing; to test particular functions or code modules. This is typically accomplished by the programmer and never by testers, as it requires detailed data of the interior program, design and code. Not at all times simply done unless the application has a well-designed architecture with tight code; could require creating test driver modules or test harnesses.

Incremental integration testing - continuous testing of an application when new functionality is added; requires that varied facets of an application's functionality be impartial enough to work separately before all elements of the program are completed, or that test drivers be developed as wanted; performed by programmers or by testers.

Integration testing - testing of mixed elements of an application to determine if they functioning collectively correctly. The 'components' might be code modules, individual applications, shopper and server applications on a network, etc. This type of testing is very related to shopper/server and distributed systems.

Functional testing - this testing is geared to functional requirements of an application; this type of testing should be carried out by testers. This does not imply that the programmers shouldn't check that their code works earlier than releasing it (which in fact applies to any stage of testing.)

System testing - this relies on the overall requirements specs; covers all the combined components of a system.

Finish-to-end testing - this is just like system testing; includes testing of an entire application atmosphere in a situation that imitate real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems.

Sanity testing or smoke testing - typically this is an preliminary testing to determine whether a new software version is performing well enough to just accept it for a major testing effort. For example, if the new software is crashing systems in each 5 minutes, making down the systems to crawl or corrupting databases, the software is probably not in a traditional condition to warrant further testing in its present state.

Regression testing - this is re-testing after bug fixes or modifications of the software. It is difficult to determine how much re-testing is needed, especially at the finish of the development cycle. Automated testing tools are very helpful for this type of testing.

Acceptance testing - this might be said as a last testing and this was accomplished based mostly on specifications of the top-person or buyer, or primarily based on use by end-users/prospects over some restricted interval of time.

Load testing - this shouldn't behing however testing an application underneath heavy loads, resembling testing a web site underneath a range of loads to find out at what level the system's response time degrades or fails.

Stress testing - the time period usually used interchangeably with 'load' and 'efficiency' testing. Additionally used to describe such tests as system functional testing while below unusually heavy loads, heavy repetition of certain actions or inputs, input of huge numerical values, massive complex queries to a database system, etc.

Performance testing - the time period often used interchangeably with 'stress' and 'load' testing. Ideally 'efficiency' testing is defined in requirements documentation or QA or Test Plans.

Usability testing - this testing is completed for 'user-buddyliness'. Clearly this is subjective, and will depend upon the focused finish-user or customer. Consumer interviews, surveys, video recording of person classes, and different strategies could be used. Programmers and testers are usually not suited as usability testers.

Compatibility testing - testing how well the software performs in a particular hardware/software/working system/network/etc. environment.

User acceptance testing - figuring out if software is satisfactory to a end-person or a customer.

Comparison testing - comparing software weaknesses and strengths to other competing products.

Alpha testing - testing an application when development is nearing completion; minor design changes should still be made as a result of such testing. This is typically achieved by end-users or others, but not by the programmers or testers.

Beta testing - testing when development and testing are essentially completed and last bugs and problems must be discovered before remaining release. This is typically carried out by end-users or others, not by programmers or testers.

If you loved this informative article and you would love to receive more details relating to tool return on investment assure visit the web page.


Contact Address

Shivshakti CHS, A-Wing, 1st Floor, Next to Sahakari Bhandar, S.K. Bole Road, Agar Bazar, Prabhadevi, Mumbai:400025
Tel: +91-22-24311614, 24311616.
FAX : +91-22-2431631,
MOB: +91-9870540453
Mail : This email address is being protected from spambots. You need JavaScript enabled to view it.

NGO | Foundation | Faith Health | Teen Care | Charitable Trust | Children Healthcare | Healthcare Senior Citizen | Teenagers | Seminars for Health Care.