Custom Search
|
|
Types Of Software Testing
The development process involves various types of testing. Each test type addresses a specific testing requirement. The most fundamental types of testing involved in the development process are: • Unit Testing • System Testing • Integration Testing • Functional Testing • Performance Testing • Beta Testing • Acceptance Testing The industry experts based upon the requirement have categorized many types of Software Testing. Following list presents a brief introduction to such types. Acceptance Testing : Is the best industry practice & its is the final testing based on specifications provided by the end-user or customer, or based on use by end-users/customers over some limited period of time. In theory when all the acceptance tests pass, it can be said that the project is done. Ad-hoc Testing: Is a commonly used term for software testing performed without planning and documentation. It is a part of exploratory testing, being the least formal of test methods. It is generally criticized because it isn't structured & the tester seeks to find bugs quickly with any means that seem appropriate. For Ad-hoc testing the testers possess significant understanding of the software before testing it. Alpha Testing: Is simulated or actual operational testing by potential users / customers or an independent test team at the developers' site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing. It is usually done when the development of the software product is nearing completion; minor design changes may still be made as a result of such testing. Beta Testing: Comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users. Thus beta testing is done by end-users or others, & not by the programmers or testers. Black Box Testing: Involves tests based upon specifications requirements and functionality. For Black Box testing, the software tester need not have any knowledge of internal design of the software or its code being tested. Due to this reason, the tester and the programmer can be independent of each other, avoiding programmer bias toward his own work. During Black Box testing, the tester would only know the Legal inputs and what the expected outputs should be, but he need not know as to how the program actually arrives at those outputs. Build Verification Testing or BVT: Build Verification Testing, also known as Build Acceptance Test, is a set of tests run on each new build of a product to verify that the build is testable before the build is released into the hands of the test team. The build acceptance test is generally a short set of tests, which exercises the mainstream functionality of the application software. Any build that fails the build verification test is rejected, and testing continues on the previous build (provided there has been at least one build that has passed the acceptance test). BVT is important because it lets developers know right away if there is a serious problem with the build, and they save the test team wasted time and frustration by avoiding test of an unstable build. For More Info to click here : Software Testing Article Directory: http://www.articledashboard.com Yogindernath Moderator (A Storehouse of Complete Knowledge on Software Testing & QA under one Roof) E-mail: software.testing.genius@gmail.com |
|