Software Testing Strategies: Software Test Case Design Methods

1591 Words7 Pages

7 Software Testing Strategies A strategy for software Testing integrates software test case design methods into a well planned Series of steps that result in successful Construction of software that result in successful construction of software. Software testing Strategies gives the road map for testing. A software testing Strategy should be flexible enough to promote a customized testing approach at same time it must be right enough. Strategy is generally developed by project managers, software engineer and testing specialist. There are four different software testing strategies. 7.1) Unit testing 7.2) Integration testing 7.3) Acceptance/Validation testing 7.4) System testing 7.1 Unit testing Testing of individual software …show more content…

User or customer do this testing to determine whether to accept application. Acceptance testing (also known as user acceptance testing) is a type of testing carried out in order to verify if the product is developed as per the standards and specified criteria and meets all the requirements specified by customer. This type of testing is generally carried out by a user/customer where the product is developed externally by another party. Acceptance testing falls under black box testing methodology where the user is not very much interested in internal working/coding of the system, but evaluates the overall functioning of the system and compares it with the requirements specified by them. User acceptance testing is considered to be one of the most important testing by user before the system is finally delivered or handed over to the end user. Acceptance testing is also known as validation testing, final testing, QA testing, factory acceptance testing and application testing etc. And in software engineering, acceptance testing may be carried out at two different levels; one at the system provider level and another at the end user …show more content…

To check whether system meets performance requirements. Used different performance and load tools to do this. Types of Performance testing: • Stress Testing • Configuration Testing • Compatibility Testing • Regression Testing • Recovery Testing • Usability Testing Stress testing System is stressed beyond its specifications to check how and when it fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load. Usability testing User-friendliness check. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing. Recovery testing Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems. Compatibility testing Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above. Comparison testing Comparison of product strengths and weaknesses with previous versions or other similar products. Regression

Open Document