What Kinds Of Software Testing Should Be Considered

What Kinds Of Software Testing Should Be Considered

Black box testing - This kind of Testing shouldn't be based mostly on any information of inner design or coding. These Tests are primarily based on necessities and functionality.

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

Unit testing - probably the most 'micro' scale of testing; to test specific features or code modules. This is typically accomplished by the programmer and never by testers, because it requires detailed data of the inner program, design and code. Not always simply finished unless the application has a well-designed architecture with tight code; might require creating test driver modules or test harnesses.

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

Integration testing - testing of mixed components of an application to find out in the event that they functioning collectively correctly. The 'elements' may be code modules, individual applications, consumer and server applications on a network, etc. This type of testing is very related to consumer/server and distributed systems.

Functional testing - this testing is geared to functional necessities of an application; this type of testing ought to be done by testers. This does not imply that the programmers should not check that their code works earlier than releasing it (which of course applies to any stage of testing.)

System testing - this relies on the overall necessities specs; covers all the mixed parts of a system.

Finish-to-finish testing - this is just like system testing; involves testing of a whole application setting in a scenario that imitate real-world use, reminiscent of 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 or not a new software version is performing well enough to just accept it for a significant testing effort. For instance, if the new software is crashing systems in every 5 minutes, making down the systems to crawl or corrupting databases, the software will not be in a normal condition to warrant further testing in its current state.

Regression testing - this is re-testing after bug fixes or modifications of the software. It is difficult to find out how much re-testing is needed, particularly at the end of the development cycle. Automated testing tools are very useful for this type of testing.

Acceptance testing - this may be said as a closing testing and this was executed based mostly on specifications of the end-user or customer, or based on use by finish-users/clients over some limited interval of time.

Load testing - this will not behing however testing an application underneath heavy loads, corresponding to testing a web site underneath a range of loads to determine at what level the system's response time degrades or fails.

Stress testing - the time period typically used interchangeably with 'load' and 'efficiency' testing. Additionally used to explain such tests as system functional testing while underneath unusually heavy loads, heavy repetition of certain actions or inputs, input of large 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 done for 'user-good friendliness'. Clearly this is subjective, and can rely on the focused end-consumer or customer. Consumer interviews, surveys, video recording of user classes, and different methods will be used. Programmers and testers are usually not suited as usability testers.

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

Consumer acceptance testing - determining if software is satisfactory to a finish-consumer or a customer.

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

Alpha testing - testing an application when development is nearing completion; minor design changes may still be made on account of such testing. This is typically accomplished by finish-customers or others, but not by the programmers or testers.

Beta testing - testing when development and testing are essentially completed and last bugs and problems should be discovered before last release. This is typically achieved by end-customers or others, not by programmers or testers.

When you beloved this short article and you want to acquire details relating to Cania Consulting kindly go to our own web site.

Donate

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.