Black field testing – This sort of Testing just isn’t based mostly on any data of inner design or coding. These Checks are based mostly on necessities and performance.
White field testing – That is based mostly on data of the inner logic of an software’s code. Checks are based mostly on protection of code statements, branches, paths, situations.
Unit testing – probably the most ‘micro’ scale of testing; to check specific features or code modules. That is sometimes achieved by the programmer and never by testers, because it requires detailed data of the inner program, design and code. Not at all times simply achieved except the appliance has a well-designed structure with tight code; might require growing take a look at driver modules or take a look at harnesses.
Incremental integration testing – steady testing of an software when new performance is added; requires that numerous points of an software’s performance be unbiased sufficient to work individually earlier than all components of this system are accomplished, or that take a look at drivers be developed as wanted; achieved by programmers or by testers.
Integration testing – testing of mixed components of an software to find out in the event that they functioning collectively appropriately. The ‘components’ may be code modules, particular person purposes, consumer and server purposes on a community, and so forth. The sort of testing is very related to consumer/server and distributed programs.
Purposeful testing – this testing is geared to purposeful necessities of an software; this sort of testing needs to be achieved by testers. This does not imply that the programmers should not verify that their code works earlier than releasing it (which in fact applies to any stage of testing.)
System testing – that is based mostly on the general necessities specs; covers all of the mixed components of a system.
Finish-to-end testing – that is much like system testing; includes testing of a whole software atmosphere in a scenario that imitate real-world use, similar to interacting with a database, utilizing community communications, or interacting with different , purposes, or programs.
Sanity testing or smoke testing – sometimes that is an preliminary testing to find out whether or not a brand new software program model is performing properly sufficient to just accept it for a significant testing effort. For instance, if the brand new software program is crashing programs in each 5 minutes, making down the programs to crawl or corrupting databases, the software program is probably not in a standard situation to warrant additional testing in its present state.
Regression testing – that is re-testing after bug fixes or modifications of the software program. It’s tough to find out how a lot re-testing is required, particularly on the finish of the event cycle. Automated testing instruments are very helpful for this sort of testing.
Acceptance testing – this may be mentioned as a closing testing and this was achieved based mostly on specs of the end-user or buyer, or based mostly on use by end-users/clients over some restricted time frame.
Load testing – that is nothing however testing an software underneath heavy masses, similar to testing a website underneath a variety of masses 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 explain such assessments as system purposeful testing whereas underneath unusually heavy masses, heavy repetition of sure actions or inputs, enter of huge numerical values, giant complicated queries to a database system, and so forth.
Efficiency testing – the time period usually used interchangeably with ‘stress’ and ‘load’ testing. Ideally ‘efficiency’ testing is outlined in necessities documentation or QA or Take a look at Plans.
Usability testing – this testing is completed for ‘user-friendliness’. Clearly that is subjective, and can depend upon the focused end-user or buyer. Consumer interviews, surveys, video recording of consumer classes, and different methods can be utilized. Programmers and testers are often not suited as usability testers.
Compatibility testing – testing how properly the software program performs in a selected /software program/working system/community/and so forth. atmosphere.
Consumer acceptance testing – figuring out if software program is passable to a end-user or a buyer.
Comparability testing – evaluating software program weaknesses and strengths to different competing merchandise.
Alpha testing – testing an software when improvement is nearing completion; minor design adjustments should still be made on account of such testing. That is sometimes achieved by end-users or others, however not by the programmers or testers.
Beta testing – testing when improvement and testing are basically accomplished and closing bugs and issues should be discovered earlier than closing launch. That is sometimes achieved by end-users or others, not by programmers or testers.
Mutation testing – a technique for figuring out a set of take a look at knowledge or take a look at circumstances is beneficial or not, by deliberately introducing numerous code adjustments (‘bugs’) and retesting with the unique take a look at knowledge/circumstances to find out if the ‘bugs’ are detected.