Gia Long

Switch to desktop

What Varieties Of Software Testing Should Be Considered

What Varieties Of Software Testing Should Be Considered

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

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

Unit testing - essentially the most 'micro' scale of testing; to test specific functions or code modules. This is typically executed by the programmer and never by testers, as it requires detailed knowledge of the internal program, design and code. Not always simply done unless the application has a well-designed architecture with tight code; may require creating test driver modules or test harnesses.

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

Integration testing - testing of combined components of an application to find out if they functioning together correctly. The 'components' may be code modules, particular person 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 necessities of an application; this type of testing must be carried out by testers. This doesn't mean that the programmers should not check that their code works earlier than releasing it (which after all applies to any stage of testing.)

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

End-to-finish testing - this is just like system testing; involves testing of an entire application setting in a state of affairs 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 model is performing well enough to simply accept it for a significant testing effort. For instance, 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 standard situation to warrant further testing in its present state.

Regression testing - this is re-testing after bug fixes or modifications of the software. It is tough to determine how a lot re-testing is required, particularly at the finish of the development cycle. Automated testing instruments are very useful for this type of testing.

Acceptance testing - this will be said as a ultimate testing and this was executed based on specs of the end-person or buyer, or based on use by finish-customers/clients over some restricted interval of time.

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

Stress testing - the term typically used interchangeably with 'load' and 'performance' testing. Additionally used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of sure actions or inputs, enter of large numerical values, giant advanced queries to a database system, etc.

Efficiency testing - the time period typically used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing is defined in requirements documentation or QA or Test Plans.

Usability testing - this testing is done for 'person-palliness'. Clearly this is subjective, and will rely on the targeted finish-consumer or customer. Consumer interviews, surveys, video recording of user classes, and different strategies will be used. Programmers and testers are normally not suited as usability testers.

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

Person acceptance testing - figuring out if software is satisfactory to a finish-consumer or a customer.

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

Alpha testing - testing an application when development is nearing completion; minor design adjustments should still be made because of such testing. This is typically achieved by finish-customers or others, however not by the programmers or testers.

Beta testing - testing when development and testing are essentially completed and closing bugs and problems need to be discovered earlier than remaining release. This is typically completed by finish-users or others, not by programmers or testers.

If you liked this post and you would like to obtain much more data regarding test management experience kindly take a look at the site.
Email: This email address is being protected from spambots. You need JavaScript enabled to view it.